Re: insight gdb all messed up...

[Keith Seitz <kseitz@firetalk.com>]

Joseph Nicholas Yarbrough wrote:
> 
> (gdb) source main.c
> main.c:1: Error in sourced command file:
> Undefined command: "".  Try "help".
> 

Ummm....

(gdb) help source
Read commands from a file named FILE.
Note that the file ".gdbinit" is read automatically in this way
when gdb is started.

The "source" command does not do what you think it does.

> that is the error... to be precise. I love asm as much as the next guy, but
> being able to see the C code can be helpfull. seeing as I debug c code. ;]
> it seems to look for init.c as the code. I renamed main.c to init.c, and list
> worked. But, when I tried to set a breakpoint with break. it broke.
> 
> any ideas on something I might be doing wrong?

Ok, I'll say the obvious thing first (just in case ;-): you compiled
with debug info, right? ("-g" to the compiler). If so, gdbtk should have
been able to find your sources. If not, try adding the path to the
sources using the "dir" command in the console window. Sorry, there is
no GUI for this yet (although I've begged for time to do it for a long
time now).

(gdb) help dir
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.

> also... thought about adding a button to rebuild packages with make?

That would be easy enough: gdb supports both a "make" command and access
to the shell. ("make" does the same thing as "shell make".)

Keith
-- 
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com