"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?

Bắt đầu bằng việc xem xét cách image slim-bullseye được build và các tùy chọn ./configure cùng LDFLAGS của nó được thiết lập ở đâu. Kiểm tra các debug-build flags được đề xuất cho Python, việc cài đặt GDB và các extension của GDB so với quy trình image hiện có. Được xem là hoàn tất khi dự án có một debug image được tài liệu hóa hoặc một phương án thay thế rõ ràng, được maintainer phê duyệt, để tạo core dump và backtrace.