Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315330

Summary: GDB Hardware debugger ignores fullpath attribuite in stack traces.
Product: [Tools] CDT Reporter: Doug Schaefer <cdtdoug>
Component: cdt-debug-cdi-gdbAssignee: Doug Schaefer <cdtdoug>
Status: RESOLVED WONTFIX QA Contact: Elena Laskavaia <elaskavaia.cdt>
Severity: normal    
Priority: P3 CC: pawel.1.piech
Version: 7.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Doug Schaefer CLA 2010-06-01 21:46:26 EDT 
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.
Comment 1 Doug Schaefer CLA 2010-06-01 21:47:18 EDT 
I'll try and dig into it more. Until the dsf/gdb remote debugger becomes more flexible, I need the hardware debugger.
Comment 2 Doug Schaefer CLA 2010-06-01 22:15:53 EDT 
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.
Comment 3 Doug Schaefer CLA 2010-08-09 13:30:07 EDT 
Forgot what this was about. Putting a note to remind me. "Android"
Comment 4 Doug Schaefer CLA 2011-01-04 14:46:32 EST 
Thinking of using TCF for Android. Kill this unless I need it later.