From: Daniel Jacobowitz <drow@false.org>
To: Andr? P?nitz <apoenitz@trolltech.com>
Cc: gdb@sources.redhat.com
Subject: Re: How to use auto-solib-add properly?
Date: Tue, 07 Oct 2008 14:02:00 -0000 [thread overview]
Message-ID: <20081007140206.GA17209@caradoc.them.org> (raw)
In-Reply-To: <200810071228.21179.apoenitz@trolltech.com>
On Tue, Oct 07, 2008 at 12:28:13PM +0200, Andr? P?nitz wrote:
> My idea was to use
>
> set auto-solib-add off
> set stop-on-solib-events 1
>
> and whenever a "shared library event" is encountered I'd do:
>
> for all shared objects except some big ones that I want to avoid do:
> sharedlibrary <lib>
> continue
Sonds like it might work.
> Is there a way to find out what exactly triggered the shared lib event?
Not in any existing version of GDB, though this is on my wishlist.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-10-07 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 10:27 André Pönitz
2008-10-07 14:02 ` 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=20081007140206.GA17209@caradoc.them.org \
--to=drow@false.org \
--cc=apoenitz@trolltech.com \
--cc=gdb@sources.redhat.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