GDB no longer works for GCC-generated executables on Sequoia? #5992
Unanswered
adah1972
asked this question in
Everyday usage
Replies: 1 comment
-
This was reported upstream 5 months ago, with no progress as of this writing: https://sourceware.org/bugzilla/show_bug.cgi?id=32235 You might want to take a look at that bug report and see if you can contribute any other insights. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Output of
brew config
Output of
brew doctor
Description of issue
Before I upgraded to Sequoia, I was able to use
g++ -gdwarf-3
to build a program, and usegdb
to debug it (though there are always hassles, like codesigning and first-time hangs). But now I cannot in Sequoia.However, the behaviour is quite complicated, and I am not even sure whom to blame: gcc, gdb, and macOS might all be involved.
-g
,-gdwarf-3
,-gdwarf-4
, among others) for gcc, setting a breakpoint on the resulting executable in gdb gives a message likeDWARF Error: DW_FORM_line_strp used without required section
.-gdwarf-3
or-gdwarf-4
with clang results in an executable usable in gdb, though using-g
will cause an error message in gdb like:DW_FORM_GNU_str_index or DW_FORM_strx used without .debug_str section in CU at offset 0x0
.So the original purpose of using gdb with gcc no longer works....
Any clues?
Beta Was this translation helpful? Give feedback.
All reactions