[Bug gdb/18629] global variable

["rbd at hawaii dot edu" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18629

--- Comment #4 from Roger Davis <rbd at hawaii dot edu> ---
Thanks Pedro, but unfortunately when I compile multiple source files separately
and then link them later, there are *NO* .dSYM directories created and thus
nothing else available to manually load into gdb as you suggested.

After thrashing around a bit more today I have discovered a workaround, but it
strikes me as uncomfortably shaky and prone to future collapse. I have been
using the MacPorts gdb beginning with the Mavericks release because at that
time gdb was removed from Xcode. I have always just used the standard MacPorts
'gdb' port since Mavericks and until now it has worked just fine without the
global variable problem, but looking through some other discussion threads I am
now aware of the MacPorts 'gdb-apple' port, which I would assume to be somehow
related to the pre-Mavericks Xcode gdb and/or the Apple gdb fork you mentioned.
I just installed gdb-apple and it seems to work fine so far, although it
produces even more warnings of the form

  warning: Could not find object file "/BinaryCache/coreTLS...

than does the current MacPorts 7.9.1 standard gdb port. The gdb-apple port
seems pretty old, however (6.3), which makes me very nervous about counting on
its continued viability.

What's still a mystery to me is why the previous MacPorts gdb 7.7.1 port did
not exhibit this bug under Xcode 6.3 but now also fails under the new Xcode 6.4
just like the current MacPorts gdb 7.9.1. At this point I think I probably need
to find someone at MacPorts to explain (and hopefully fix!) things.

Thanks,

Roger

-- 
You are receiving this mail because:
You are on the CC list for the bug.