From: Igor Korot <ikorot@earthlink.net>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb@sourceware.org
Subject: Re: What do I need to look at the source while debugging?
Date: Thu, 12 Jun 2008 04:34:00 -0000 [thread overview]
Message-ID: <28475522.1213245246917.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net> (raw)
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.
>
>
next reply other threads:[~2008-06-12 4:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 4:34 Igor Korot [this message]
-- 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 16:06 Igor Korot
2008-06-16 16:41 ` Daniel Jacobowitz
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-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=28475522.1213245246917.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net \
--to=ikorot@earthlink.net \
--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