-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include gdb alongside modern gcc versions #62
Comments
@nega0 dumps of gdb 7.6 and 13.2 output gdb_output.txt The cext binary should have DWARF version 4
|
oops. hitting the post button helps. |
RHEL8 comes with gdb 8, so this is a RHEL7 only issue. I see two main solutions:
|
I'm in favor of option 2, since there seem to be other bugs created by having modern compiler toolchain and old gdb versions, and it's up to the OS to backport patches. For example, stock gdb 8.2 (the version in alma8) fails to load binaries compiled under py3-v4.3 because of this bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23919 and I'm not sure if alma8 backports the fix or not (I don't think it does based on the files in https://git.almalinux.org/rpms/gdb/src/branch/c8/SOURCES). I'm guessing some other incompatibility is making the provided gdb 7 not recognize the DWARF version even with It makes sense to keep the whole C/C++ toolchain (gcc, make, bison, binutils, autotools, gdb whatever) consistent. |
The ancient version of gdb (7.6.1) on the cobalts and NPX isn't able to read the debug info in the
py3-v4.3
preventing debugging. This is at least partially because gcc 11 switched the default DWARF version from 4 to 5, which is only supported in gdb 8 and later.In my case, recompiling the python extension with
-gdwarf-4
did NOT fix the issues. Including a gdb version >=8 alongside gcc 13 should work.The text was updated successfully, but these errors were encountered: