#48284: gdb @7.9.1_0: cannot determine type of primitive global variables ----------------------+------------------------------- Reporter: rbd@… | Owner: stuartwesterman@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: invalid | Keywords: Port: gdb | ----------------------+------------------------------- Comment (by rbd@…): Thanks for figuring that out, Stuart, it hadn't occurred to me to try that. I can certainly use it as a workaround when needing to debug something without otherwise changing my build procedure, and that's definitely useful. Two points, however: (1) As noted in my original post, the gdb from the current MacPorts gdb- apple port works perfectly well on my example without me having to manually run dsymutil on my executable. Clearly, that version of gdb is somehow able to locate my global symbols in a way which the standard gdb 7.9.1 cannot. I think that is a 7.9.1 deficiency which ought to be fixed. (2) Every single one of my cc commands includes the -g flag, including each of the .c to .o compiles and the final .o link command. It's rather lame IMHO that after all that I then have to use dsymutil, essentially saying 'No, fellas, I was actually really serious about wanting to be able save all my symbols for debugging purposes just like I said I did the first time.' I have never seen any cc compiling environment require this kind of nonsense, and I've seen a bunch of cc compiling environments. This may be as much a MacOS cc issue (or maybe more generally a clang problem) as a gdb problem, and I will see how far I get with Apple on filing a bug report on their end on this cc behavior. Thanks again for your workaround, but I hope you will reconsider closure of this bug report given the fact that enough symbol information is being stored somewhere such that gdb-apple can make sense of it where gdb 7.9.1 cannot. Roger -- Ticket URL: <https://trac.macports.org/ticket/48284#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X