mirror of
https://github.com/bminor/binutils-gdb.git
synced 2025-11-16 12:34:43 +00:00
abe6b29caf
Today, GDB links against the Python library using the unstable API. This approach causes portability issues of the generated GDB artifact. Indeed the built artifact is tighly coupled with the specific version of Python that it was compiled with. Using a slighly minor version of Python can cause unpredictable crashes at runtime due to ABI instability between the Python versions, even minor ones. The solution would consist in restricting the usage of Python functions to the limited C API controlled via Py_LIMITED_API that must be defined before the inclusion of <Python.h>. This patch does not aim at porting the whole GDB codebase to the Python limited C API, but rather enabling a development mode where developers can experiment with the Python limited C API, and fix issues. This development mode is accessible with the configure option --enable-py-limited-api which is set by default to 'no'. Note: the version of the Python limited API is currently set to 3.11 because of PyBuffer_FillInfo and PyBuffer_Release. This choice is not frozen, and could be reviewed later on depending on newly discovered issues during the migration. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23830 Approved-By: Tom Tromey <tom@tromey.com>
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README, and so on. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.