"debug build" for at least one image

Recently we had a C extension for python failing in production in an environment that we do not own ourselves. The data in that environment was causing the issues. Because for that reason, it was complicated to reproduce it in different environments, we looked into running a debug version of python in that environment to understand where it was crashing, but that turned out quite complicated to do.

In the end I managed to home in on the data issues, set up data locally to reproduce it and build a debug version of the slim-bullseye image that I could use as a source for our application image. This allowed us to dump a core and investigate the back traces.

Would it be helpful to have at least one image that contains a debug build of python in this stack, so that it's easier for developers to switch to that image and do this analysis?

An image that adds these lines to .,/configure

--with-pydebug \ CFLAGS="-g -O0" \

and sets LDFLAGS="" instead of LDFLAGS="-Wl,--strip-all"; \ ,

installs gdb and gdb extensions (# enable GDB to load debugging data: https://github.com/docker-library/python/pull/701)

If that's not a good idea, could you let me know what you'd recommend otherwise as a better process?

Commencez par examiner comment l’image slim-bullseye est construite et où ses options ./configure et LDFLAGS sont définies. Vérifiez les flags de compilation en mode debug proposées pour Python, l’installation de GDB et les extensions de GDB par rapport au processus d’image existant. C’est terminé lorsque le projet dispose d’une image de debug documentée ou d’une alternative claire approuvée par un maintainer pour produire des core dumps et des backtraces.