From: Igor Korot <ikorot@earthlink.net>
To: Fahd Abidi <fabidi@ultsol.com>, Michael Snyder <msnyder@specifix.com>
Cc: gdb@sourceware.org
Subject: RE: What do I need to look at the source while debugging?
Date: Mon, 16 Jun 2008 16:06:00 -0000 [thread overview]
Message-ID: <14479600.1213632371027.JavaMail.root@elwamui-little.atl.sa.earthlink.net> (raw)
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.
>>
>>
>
>
>
next reply other threads:[~2008-06-16 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 16:06 Igor Korot [this message]
2008-06-16 16:41 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 18:42 Igor Korot
2008-06-16 17:17 Igor Korot
2008-06-16 17:38 ` Michael Snyder
2008-06-16 4:50 Igor Korot
2008-06-16 1:09 Fahd Abidi
2008-06-15 21:53 Igor Korot
2008-06-15 22:27 ` Michael Snyder
2008-06-15 4:02 Igor Korot
2008-06-15 20:06 ` Michael Snyder
2008-06-12 4:34 Igor Korot
2008-06-11 17:54 Igor Korot
2008-06-11 18:44 ` Michael Snyder
2008-06-11 16:26 Igor Korot
2008-06-11 17:16 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14479600.1213632371027.JavaMail.root@elwamui-little.atl.sa.earthlink.net \
--to=ikorot@earthlink.net \
--cc=fabidi@ultsol.com \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox