Help with Code in Multiple Directories

[Nirf]

Hello,
I'm trying to get started with GDB but am having great trouble. I have a fairly complicated program with code spread out over several directories and GDB is refusing to recognize that I have any source at all. I have also tried GDB on a hello world program and in that case it worked. To specify the directory structure, I have:
.../UnixBuild/         which contains the make file and the executable
.../HysteresisFiles/      which contains most of the source
.../Console/              which contains the rest

i go into the konsole, go into UnixBuild and run gdb. Then I enter in the commands "directory .../HysteresisFiles/" and then "directory .../Console/" (at this point I should probably clarify that ... stands for the base directory that I am typing in in full). Then I type "file HysteresisConsole" which is the name of my executable. It loads fine and I am able to run it. However when I type in a command like "list sourcecodename:5" it does not find the source code regardless of which file name I insert for sourcecodename. Any help with this would be greatly appreciated.

Nir

[Paul Pluzhnikov-4]

On Fri, Mar 27, 2009 at 1:43 AM, Nirf <quicknir@...> wrote:

> I'm trying to get started with GDB but am having great trouble.

On what platform? Using which version of GDB?

Note that on Linux, or any other platform that uses DWARF
debug format, you shouldn't need to specify 'directory ...'
at all if you build and debug on the same machine: compiler
already supplies all the info GDB needs to find sources
regardless of where in file system they are located.

> However when I type in a command like "list sourcecodename:5" it does not
> find the source code regardless of which file name I insert for
> sourcecodename.

Did you build your program with debugging info (the '-g' GCC option) ?

Cheers,
--
Paul Pluzhnikov

[Paul Pluzhnikov-4]

Summary for the list:

On Fri, Mar 27, 2009 at 8:33 AM, Paul Pluzhnikov <ppluzhnikov@...> wrote:
> Did you build your program with debugging info (the '-g' GCC option) ?


We discovered that this indeed was the cause: Nir added '-g'
to CFLAGS, but neglected to do 'make clean' and only relinked his binary.

--
Paul Pluzhnikov