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

首先检查 slim-bullseye 镜像的构建方式，以及其 ./configure 选项和 LDFLAGS 的设置位置。根据现有镜像流程，检查提议的 Python 调试构建标志、GDB 安装和 GDB 扩展。完成的标准是：项目拥有已记录文档的调试镜像，或拥有一种明确且经 maintainer 批准的替代方案，用于生成 core dump 和 backtrace。