Member Discussions

Hiya all.

When using gnu debugger on a friend's game, I'm getting the following problem:

I can use the command 'bt' to get my backtraced functions that led up to the crash recorded in the core file, but I can't select a single frame for more information. When I do, I get the following ...

(gdb) frame 13
#13 0x08049e20 in main (argc=4, argv=0x58b2e390) at comm.c:158
158 comm.c: No such file or directory.
in comm.c


This occurs no matter which frame I try to select. I don't know if they've ever used gnu debugger to debug their program. Can anyone tell me what's happening here, and how I would go about fixing it?

I'm not 100% sure of this, because I can't reproduce the problem on my system which has the latest gdb, but I think in older versions you had to run gdb from the same directory the source files are in. I remember seeing error messages like that when I was running it from some other directory.

Yes! You are completely right. That solved the problem. I'm sure there has to be an option somewhere to tell gnu debugger where the source files are located, however. Well... until I find that, or they update their debugger, this is a fine fix.

Thanks!

(gdb) help directory
Add directory DIR to beginning of search path for source files.
Forget cached info on source file locations and line positions.
DIR can also be $cwd for the current working directory, or $cdir for the
directory in which the source file was compiled into object code.
With no argument, reset the search path to $cdir:$cwd, the default.