From: Pupeno <pupeno@pupeno.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: debugging dynamically loadable code
Date: Mon, 03 Apr 2006 21:23:00 -0000 [thread overview]
Message-ID: <200604032321.42906.pupeno@pupeno.com> (raw)
In-Reply-To: <20060403163456.GA9232@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Monday, 3 de April de 2006 18:34, Daniel Jacobowitz wrote:
> On Mon, Apr 03, 2006 at 06:09:33PM +0200, Pupeno wrote:
> > Any ideas how can I do my debugging ?
>
> You can do one of two things here:
>
> - "set stop-on-solib-events 1". This will cause GDB to stop when
> shared libraries are loaded or unloaded. You can use "info shared" to
> see if the library you want has been loaded after a stop.
It halted the process very soon, maybe some loading I was not aware of and I
was not sure how to continue.
> - Pending breakpoints. You can set a breakpoint by filename:line or
> function name, even if that object hasn't been loaded yet -
Oh, that worked, particurarly breakpoint on filename:line. I tried pending
breakpoints once but it didn't work, it just didn't break, now it worked like
a charm.
> you just
> may not be able to do it using the DDD GUI. You need GDB 6.3 or 6.4
> for this to work. I don't know if DDD lets you get at the GDB console
> usefully.
Yes, I can do it, DDD let's you access gdb console, sometimes it behaves
funny, but the data show makes it worth it.
Thank you.
--
Pupeno <pupeno@pupeno.com> (http://pupeno.com)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-03 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 16:09 Pupeno
2006-04-03 16:35 ` Daniel Jacobowitz
2006-04-03 21:23 ` Pupeno [this message]
2006-04-03 21:27 ` Daniel Jacobowitz
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=200604032321.42906.pupeno@pupeno.com \
--to=pupeno@pupeno.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).