From: Daniel Jacobowitz <drow@false.org>
To: Pupeno <pupeno@pupeno.com>
Cc: gdb@sourceware.org
Subject: Re: debugging dynamically loadable code
Date: Mon, 03 Apr 2006 21:27:00 -0000 [thread overview]
Message-ID: <20060403212711.GA15936@nevyn.them.org> (raw)
In-Reply-To: <200604032321.42906.pupeno@pupeno.com>
On Mon, Apr 03, 2006 at 11:21:35PM +0200, Pupeno wrote:
> 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.
You can just say continue and try info shared again, until you see the
library you want. Anyway, if pending breakpoints work for you, use
those instead.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-04-03 21:27 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
2006-04-03 21:27 ` Daniel Jacobowitz [this message]
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=20060403212711.GA15936@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pupeno@pupeno.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