Open smathermather opened 4 hours ago
I don't think that would be appropriate; rebuilding the image with debugging symbols for the specific module that is giving issues (if needed) would be better.
Or use ./start-dev-env.sh
and rebuild just the module you need with debugging symbols turned on (that's what I usually do).
I have someone helping with a testing environment for running test datasets through the pipeline when there are changes to the code base, a bit CI/CD style. @pierotofy: Is it appropriate or problematic to add debugging symbols to the default docker builds to facilitate this?