Community
Participate
Working Groups
In GDB 7.1, the file attribute has the short name that the compiler has and the fullname gives you the full path the gdb has figured out for the local file. The gdb hardware debugger doesn't seem to be picking up either.
I'll try and dig into it more. Until the dsf/gdb remote debugger becomes more flexible, I need the hardware debugger.
Actually, later on in my session it picked it up fine. I think it was the order in which events occurred. The debugger paused on start up before the gdb knew where the source paths were. Later on, it finds out via the run commands I gave it. The stack event is pushed out again but we don't update the debug view with it. At any rate, this isn't very critical since I'm kinda abusing the launcher for something it wasn't intended fore.
Forgot what this was about. Putting a note to remind me. "Android"
Thinking of using TCF for Android. Kill this unless I need it later.