MacOs/11.4 GDB 10.2 from Homebrew using either Eclipse/CDT 2021.06 or command-line causing error: (gdb) file /Users/sam/eclipse-workspace/Eclipse.HelloWorld.MacOS.Gcc/Debug/Eclipse.HelloWorld.MacOS.Gcc Reading symbols from /Users/sam/eclipse-workspace/Eclipse.HelloWorld.MacOS.Gcc/Debug/Eclipse.HelloWorld.MacOS.Gcc... ../../gdb/thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion `current_thread_ != nullptr' failed. yet, if I elect to not stop, and continue I can set breakpoints and control execution of the binary: ../../gdb/thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion `current_thread_ != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n Command aborted. (gdb) b main Breakpoint 1 at 0x10000270f: file ../src/Eclipse.HelloWorld.MacOS.Gcc.temp.cpp, line 22. (gdb) bl Undefined command: "bl". Try "help". (gdb) run Starting program: /Users/sam/eclipse-workspace/Eclipse.HelloWorld.MacOS.Gcc/Debug/Eclipse.HelloWorld.MacOS.Gcc [New Thread 0x2203 of process 4658] [New Thread 0x1b03 of process 4658] warning: unhandled dyld version (17) Thread 2 hit Breakpoint 1, main (argc=1, argv=0x7ffeefbffa68) at ../src/Eclipse.HelloWorld.MacOS.Gcc.temp.cpp:22 22 mainPhilosopher();
I should add that when I use GDB where I put the application to be debugged on the command line of a Terminal within OS-X, everything functions flawlessly. It's only when I use the "file" command or the equivalent GDB/MI command that the 'null pointer" issue shows up. ( GDB app in my install has been fully enabled to execute with 'code signing' instructions.) What prompted my investigation in narrowing down the problem was the GDB/MI seemed to be having some issue, later I found it was simply the 'file' command. Sam
anything I should be doing to enable the status to change to "Confirmed"?
Looks like a duplicate of https://sourceware.org/bugzilla/show_bug.cgi?id=26912 (and https://sourceware.org/bugzilla/show_bug.cgi?id=27365).
yes - 26912 (while different compilers/etc) is experiencing the same issue *** This bug has been marked as a duplicate of bug 26912 ***