What do I need to look at the source while debugging?

[Igor Korot]

Hi,
I just tried to use a 'load' command:

(gdb) load /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverManager/SQLDriverConnectW.c
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
You can't do that when your target is `multi-thread'

What does this mean? I just used KDdevelop to create a project...

and simply trying:

(gdb) break /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverManager/SQLDriverConnect.c:616
No source file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverManager/SQLDriverConnect.c.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 2 (/home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverManager/SQLDriverConnect.c:616) pending.

However the file exists and I have a reading permission...

Thank you.

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 11, 2008 2:44 PM
>To: Igor Korot <ikorot@earthlink.net>
>Cc: gdb@sourceware.org
>Subject: Re: What do I need to look at the source while debugging?
>
>On Wed, 2008-06-11 at 10:53 -0700, Igor Korot wrote:
>
>> >If not, you can override gdb's source file search path by using the
>> >"dir" command (see "help dir")
>> 
>> You mean like this:
>> 
>> gdb myprogram
>> gdb> dir /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers
>> 
>> right?
>
>Right.
>
>