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

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

[Igor Korot]

Hi, Michael,

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 11, 2008 10:15 AM
>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 09:26 -0700, Igor Korot wrote:
>> Hi, ALL,
>> First a question: Is there anybody that using Gentoo + Portage?
>> 
>> And now to the problem:
>> 
>> I have a Gentoo box installed. On it I have a GNOME with KDevelop,
>> wxGTK, unixODBC and gdb. GNOME, KDevelop and gdb installed through
>> Portage. wxGTK is hand compiled and installed.
>> I installed unixODBC-2.2.12 using following:
>> 
>> 'PORTAGE_TMPDIR=/home/igor FEATURES="noclean keepwork" emerge unixODBC'
>> 
>> Then I change permissions on the /home/igor/portage/dev-db directory
>> to make it accessible to my user 'igor'.
>> Next, I started KDevelop, open the file /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c (it did open fine).
>> I put a breakopint in that function, and started my program.
>> At this point I received following message:
>> 
>> no file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c.
>
>Is that the correct location of your source files?

Yes, it is.

>
>If so, could there be a directory along that path in which user 'igor'
>does not have read permission?

If user 'igor' wouldn't have a read permission I won't be able to open this
file in KDevelop IDE.

>
>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?

>
>Michael

Thank you.
>
>

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

[Michael Snyder]

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.

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

[Igor Korot]

Hi, Michael,

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 16, 2008 10:38 AM
>To: Igor Korot <ikorot@earthlink.net>
>Cc: Daniel Jacobowitz <drow@false.org>, Fahd Abidi <fabidi@ultsol.com>, gdb@sourceware.org
>Subject: Re: What do I need to look at the source while debugging?
>
>On Mon, 2008-06-16 at 10:16 -0700, Igor Korot wrote:
>> Hi, Daniel,
>> 
>> -----Original Message-----
>> >From: Daniel Jacobowitz <drow@false.org>
>> >Sent: Jun 16, 2008 9:41 AM
>> >To: Igor Korot <ikorot@earthlink.net>
>> >Cc: Fahd Abidi <fabidi@ultsol.com>, Michael Snyder <msnyder@specifix.com>, gdb@sourceware.org
>> >Subject: Re: What do I need to look at the source while debugging?
>> >
>> >On Mon, Jun 16, 2008 at 09:06:10AM -0700, Igor Korot wrote:
>> >> >You will need to attach this gdb session to a gdbserver to begin the
>> >> >debugging. So start your application with the following commands:
>> >> >
>> >> >linux# gdbserver SQLDriverConnectW.o
>> >> >
>> >> >I forget the exact command to give to gdbserver to specify what port you
>> >> >will use to connect. Next from gdb connect to the gdbserver:
>> >> >
>> >> >(gdb) target remote ****your connection settings****
>> >
>> >FYI, this is for remote debugging.  Igor, I believe you're using
>> >native debugging, so this does not apply.
>> 
>> Yes, I'm using native debugging, ie locally.
>
>Igor, I generally don't like it when other people tell me
>"rtfm", but it sounds a little like you haven't read the
>documentation very carefully, and that that might be a
>reasonable next step for you.

I'm sorry, I guess I hit the "Send" button too fast.
And yes, I'm not very familiar with the gdb, I'm just using it locally to debug
my program. But I guess I should'nt said that comment, and you' re absolutely correct.

Thank you and I am not offended at all.
>
>
>

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

[Igor Korot]

Hi, Daniel,

-----Original Message-----
>From: Daniel Jacobowitz <drow@false.org>
>Sent: Jun 16, 2008 9:41 AM
>To: Igor Korot <ikorot@earthlink.net>
>Cc: Fahd Abidi <fabidi@ultsol.com>, Michael Snyder <msnyder@specifix.com>, gdb@sourceware.org
>Subject: Re: What do I need to look at the source while debugging?
>
>On Mon, Jun 16, 2008 at 09:06:10AM -0700, Igor Korot wrote:
>> >You will need to attach this gdb session to a gdbserver to begin the
>> >debugging. So start your application with the following commands:
>> >
>> >linux# gdbserver SQLDriverConnectW.o
>> >
>> >I forget the exact command to give to gdbserver to specify what port you
>> >will use to connect. Next from gdb connect to the gdbserver:
>> >
>> >(gdb) target remote ****your connection settings****
>
>FYI, this is for remote debugging.  Igor, I believe you're using
>native debugging, so this does not apply.

Yes, I'm using native debugging, ie locally.
>
>It sounds like your problem is specific to the Gentoo build system.
>Have you considered trying a Gentoo list?  Maybe someone there will
>recognize it.

That's why in the first message of the thread I asked if anybody here
runs Gentoo. ;-)
Anyway, I tried Gentoo forum, and I guess I will (have to) do that again.
>
>-- 
>Daniel Jacobowitz
>CodeSourcery

Thank you.

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

[Michael Snyder]

On Mon, 2008-06-16 at 10:16 -0700, Igor Korot wrote:
> Hi, Daniel,
> 
> -----Original Message-----
> >From: Daniel Jacobowitz <drow@false.org>
> >Sent: Jun 16, 2008 9:41 AM
> >To: Igor Korot <ikorot@earthlink.net>
> >Cc: Fahd Abidi <fabidi@ultsol.com>, Michael Snyder <msnyder@specifix.com>, gdb@sourceware.org
> >Subject: Re: What do I need to look at the source while debugging?
> >
> >On Mon, Jun 16, 2008 at 09:06:10AM -0700, Igor Korot wrote:
> >> >You will need to attach this gdb session to a gdbserver to begin the
> >> >debugging. So start your application with the following commands:
> >> >
> >> >linux# gdbserver SQLDriverConnectW.o
> >> >
> >> >I forget the exact command to give to gdbserver to specify what port you
> >> >will use to connect. Next from gdb connect to the gdbserver:
> >> >
> >> >(gdb) target remote ****your connection settings****
> >
> >FYI, this is for remote debugging.  Igor, I believe you're using
> >native debugging, so this does not apply.
> 
> Yes, I'm using native debugging, ie locally.

Igor, I generally don't like it when other people tell me
"rtfm", but it sounds a little like you haven't read the
documentation very carefully, and that that might be a
reasonable next step for you.

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

[Igor Korot]

Hi, Fahd,

-----Original Message-----
>From: Fahd Abidi <fabidi@ultsol.com>
>Sent: Jun 15, 2008 6:08 PM
>To: Igor Korot <ikorot@earthlink.net>, Michael Snyder <msnyder@specifix.com>
>Cc: gdb@sourceware.org
>Subject: RE: What do I need to look at the source while debugging?
>
>First make sure that your program file (SQLDriverConnectW.o) is build
>with debug symbols. to accomplish this make sure you pass the "-g" flag
>into gdb. Then open gdb with the following arguments:
>
>linux# gdb SQLDriverConnectW.o

So, basically, it's going to be:

linux# gdb -g my_program_name

right? Or is it libodbcinst.so as this file is part of the unixODBC project
and part of libodbcinst.so library?

And my application just uses this library as "DLL".

For an explanation, see my reply to latest Michael's E-mail.

>You will need to attach this gdb session to a gdbserver to begin the
>debugging. So start your application with the following commands:
>
>linux# gdbserver SQLDriverConnectW.o
>
>I forget the exact command to give to gdbserver to specify what port you
>will use to connect. Next from gdb connect to the gdbserver:
>
>(gdb) target remote ****your connection settings****
>
>
>Fahd Abidi

Thank you.
>
>-----Original Message-----
>From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
>Behalf Of Igor Korot
>Sent: Sunday, June 15, 2008 12:30 AM
>To: Michael Snyder
>Cc: gdb@sourceware.org
>Subject: Re: What do I need to look at the source while debugging?
>
>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/DriverMan
>ager/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/DriverMan
>ager/SQLDriverConnect.c:616
>No source file named
>/home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMan
>ager/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/DriverMa
>nager/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 
>>> gdb> /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/D
>>> gdb> rivers
>>> 
>>> right?
>>
>>Right.
>>
>>
>
>
>

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

[Daniel Jacobowitz]

On Mon, Jun 16, 2008 at 09:06:10AM -0700, Igor Korot wrote:
> >You will need to attach this gdb session to a gdbserver to begin the
> >debugging. So start your application with the following commands:
> >
> >linux# gdbserver SQLDriverConnectW.o
> >
> >I forget the exact command to give to gdbserver to specify what port you
> >will use to connect. Next from gdb connect to the gdbserver:
> >
> >(gdb) target remote ****your connection settings****

FYI, this is for remote debugging.  Igor, I believe you're using
native debugging, so this does not apply.

It sounds like your problem is specific to the Gentoo build system.
Have you considered trying a Gentoo list?  Maybe someone there will
recognize it.

-- 
Daniel Jacobowitz
CodeSourcery

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

[Igor Korot]

Michael,
Problem is:
1. I'm using Gentoo Linux.
2. I compiled and installed wxGTK from sources trunk.
3. I compiled and installed unixODBC-2.2.12 from Portage using this:

PORTAGE_TMPDIR=/home/igor FEATURES=keepwork emerge unixODBC

4. I have KDevelop and gdb installed.
5. Using KDevelop I created an application using wxGTK (wxWidgets) library.
6. This library is linking with odbc.so and odbcinst.so. It compiles and runs fine.
7. Using gdb I can freely step through my own program sources and wxGTK sources either when run from KDevelop or from console (GNOME or KDE).
8. However, stepping into unixODBC sources is impossible. It says "no source file...".

unixODBC sources are present in the directory /home/igor/portage/unixODBC-2.2.12/work/unixODBC-2.2.12 and they are accessible for the current user.

That's pretty much have it.

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 15, 2008 3:27 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 Sun, 2008-06-15 at 14:52 -0700, Igor Korot wrote:
>> OK, so what else can I try?
>> Do I need to reconfigure and re-build?
>
>I'm sorry, but I've lost the thread of what you're trying to do.
>Something to do with viewing your source files, but I'm not sure
>if we can help you unles we can reproduce your problem.
>
>Can you reduce this to a minimal test case?
>One that should not involve having to use
>any particular environment outside of gdb
>in order to reproduce it?
>
>
>
>
>

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

[Fahd Abidi]

First make sure that your program file (SQLDriverConnectW.o) is build
with debug symbols. to accomplish this make sure you pass the "-g" flag
into gdb. Then open gdb with the following arguments:

linux# gdb SQLDriverConnectW.o
You will need to attach this gdb session to a gdbserver to begin the
debugging. So start your application with the following commands:

linux# gdbserver SQLDriverConnectW.o

I forget the exact command to give to gdbserver to specify what port you
will use to connect. Next from gdb connect to the gdbserver:

(gdb) target remote ****your connection settings****


Fahd Abidi

-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
Behalf Of Igor Korot
Sent: Sunday, June 15, 2008 12:30 AM
To: Michael Snyder
Cc: gdb@sourceware.org
Subject: Re: What do I need to look at the source while debugging?

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/DriverMan
ager/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/DriverMan
ager/SQLDriverConnect.c:616
No source file named
/home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMan
ager/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/DriverMa
nager/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 
>> gdb> /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/D
>> gdb> rivers
>> 
>> right?
>
>Right.
>
>

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

[Igor Korot]

OK, so what else can I try?
Do I need to reconfigure and re-build?

Thank you.

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 15, 2008 1:06 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 Sun, 2008-06-15 at 00:02 -0400, Igor Korot wrote:
>> 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
>
>Why?  That's not at all what it's for.
>You never "load" a source file": "load" actually means
>"download a binary image onto a development board".
>
>
>
>

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

[Michael Snyder]

On Sun, 2008-06-15 at 14:52 -0700, Igor Korot wrote:
> OK, so what else can I try?
> Do I need to reconfigure and re-build?

I'm sorry, but I've lost the thread of what you're trying to do.
Something to do with viewing your source files, but I'm not sure
if we can help you unles we can reproduce your problem.

Can you reduce this to a minimal test case?
One that should not involve having to use
any particular environment outside of gdb
in order to reproduce it?

Re: 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.
>
>

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

[Michael Snyder]

On Sun, 2008-06-15 at 00:02 -0400, Igor Korot wrote:
> 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

Why?  That's not at all what it's for.
You never "load" a source file": "load" actually means
"download a binary image onto a development board".

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

[Igor Korot]

Michael,

-----Original Message-----
>From: Michael Snyder <msnyder@specifix.com>
>Sent: Jun 11, 2008 11:44 AM
>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?

I tried that.
The gdb says exactly the same thing.

Now, when I try just run the program under KDevelop + gdb (i.e. hit F9 in KDevelop), go to the
call I am looking for and hit F11 (step in), I receive following message:

"Debugger reported following error.

Warning: Cannot insert breakpoint 0. Error accessing memory address
0xnnnnnnnn. Input/output error.
"

Any suggestions?

I can freely step through the wxGTK code, as it is compiled by hand...

Thank you.

>
>Right.
>
>

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

[Igor Korot]

Hi, ALL,
First a question: Is there anybody that using Gentoo + Portage?

And now to the problem:

I have a Gentoo box installed. On it I have a GNOME with KDevelop,
wxGTK, unixODBC and gdb. GNOME, KDevelop and gdb installed through
Portage. wxGTK is hand compiled and installed.
I installed unixODBC-2.2.12 using following:

'PORTAGE_TMPDIR=/home/igor FEATURES="noclean keepwork" emerge unixODBC'

Then I change permissions on the /home/igor/portage/dev-db directory
to make it accessible to my user 'igor'.
Next, I started KDevelop, open the file /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c (it did open fine).
I put a breakopint in that function, and started my program.
At this point I received following message:

no file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c.

No my questions are:
1. What else is required in order to follow through the source code?
2. Do I have to run the program from the unixODBC source directory?
3. Maybe I just need to change a permissions/ownership of the source tree
of unixODBC files?

Thank you.

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

[Michael Snyder]

On Wed, 2008-06-11 at 09:26 -0700, Igor Korot wrote:
> Hi, ALL,
> First a question: Is there anybody that using Gentoo + Portage?
> 
> And now to the problem:
> 
> I have a Gentoo box installed. On it I have a GNOME with KDevelop,
> wxGTK, unixODBC and gdb. GNOME, KDevelop and gdb installed through
> Portage. wxGTK is hand compiled and installed.
> I installed unixODBC-2.2.12 using following:
> 
> 'PORTAGE_TMPDIR=/home/igor FEATURES="noclean keepwork" emerge unixODBC'
> 
> Then I change permissions on the /home/igor/portage/dev-db directory
> to make it accessible to my user 'igor'.
> Next, I started KDevelop, open the file /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c (it did open fine).
> I put a breakopint in that function, and started my program.
> At this point I received following message:
> 
> no file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/Drivers/SQLConfigDataSource.c.

Is that the correct location of your source files?

If so, could there be a directory along that path in which user 'igor'
does not have read permission?

If not, you can override gdb's source file search path by using the
"dir" command (see "help dir")

Michael