File name and line number information is buried in the debugging
information, it has no relation at all to the source text (and
couldn't, without the debugger recompiling the source to work out
where in the object code that line fell).
To find out where gdb thinks the sources should be, just say 'list'.
You should get an error telling you which file couldn't be found.
= Mike
On Jun 14, 2005, at 5:41 PM, Jim Wintermyre wrote:
Thanks for the response Mike. What's weird is that the sources
*should* be in the same location, I think. I'm building from a PGP
disk image. I tried both building on the target machine and
copying the disk image file to the debug machine, and building
directly on the debug machine, and had the same issue both times.
It seems maybe there's something weird about using a disk image,
but I know this worked fine in the past (though it's been a while
since I had to break out the two-machine debugging tools... so was
probably running the debug machine on an earlier OS; current setup
was debug machine running 10.3.9, target machine running 10.2.6).
Is there a way to see where gdb thinks the source files
corresponding to the symbol files live? It also seems weird that I
can successfully set a breakpoint by specifying the file and line
number, yet can't see the source when the breakpoint is hit.
Thanks,
Jim
At 2:10 PM -0700 6/12/05, Mike Smith wrote:
On Jun 9, 2005, at 7:30 PM, Jim Wintermyre wrote:
I'm having a problem with 2-machine debugging that I don't recall
happening before. I can't seem to view any of my source in gdb.
It gives me errors saying the file can't be found. However, the
weird thing is that once I load my symbol files I can set
breakpoints by line numbers in the file, i.e. "b foo.c:24", and
that works just fine. The breakpoints are hit correctly, but I
still can't view the corresponding source. Any ideas?
Make sure that the sources you want to look at are in the same
location they were when the module was built. You can use the
'dir' command in gdb to add a directory to the search path;
individual files (not subpaths) are looked for there as well.
