From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: breakpoints in shared libraries
Date: Tue, 13 Nov 2001 10:11:00 -0000 [thread overview]
Message-ID: <87n11a7fbd.fsf@creche.redhat.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Sun, 25 Nov 2001 13:37:12 -0500"
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>> How can this be fixed? I don't know the answer. One idea I had is to
>> annotate each breakpoint with information about what shared library it
>> comes from. Then, defer processing for that breakpoint until the
>> shared library is actually loaded by the inferior.
Daniel> I think the best approach for this is to expose an interface
Daniel> to create shlib_disabled breakpoints. Then they'll be
Daniel> automatically re-enabled when the library containing that
Daniel> symbol is loaded.
One thing to think about is how Insight will determine that it should
save a breakpoint as shlib_disabled as opposed to the ordinary kind.
At the time Insight is saving the session, all libraries may be loaded
and all the breakpoints activated.
Tom
next prev parent reply other threads:[~2001-11-25 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 9:05 Tom Tromey
2001-11-13 9:41 ` Daniel Jacobowitz
2001-11-13 10:11 ` Tom Tromey [this message]
2001-11-13 10:20 ` Per Bothner
2006-02-14 16:29 Florian Hackenberger
2006-02-14 17:00 ` Daniel Jacobowitz
2006-02-14 17:10 ` Florian Hackenberger
2006-02-14 17:13 ` Daniel Jacobowitz
2006-02-14 17:52 ` Paul Koning
2006-02-14 18:00 ` Florian Hackenberger
2006-02-14 17:21 ` Mark Kettenis
2006-02-14 17:23 ` Bob Rossi
2006-02-14 17:31 ` Daniel Jacobowitz
2006-02-14 17:47 ` Mark Kettenis
2006-02-14 17:08 ` Mark Kettenis
2006-02-14 17:20 ` Florian Hackenberger
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=87n11a7fbd.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@mvista.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