From: Tom Tromey <tromey@redhat.com>
To: Klee Dienes <klee@apple.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] add 'save-breakpoints' command
Date: Wed, 05 Dec 2001 14:06:00 -0000 [thread overview]
Message-ID: <87d71t8gke.fsf@creche.redhat.com> (raw)
In-Reply-To: Klee Dienes's message of "Tue, 04 Dec 2001 13:43:53 -0500"
>>>>> "Klee" == Klee Dienes <klee@apple.com> writes:
Klee> The 'future-break' command allows one to specify a breakpoint
Klee> that starts off as 'shlib_disabled' instead of generating an
Klee> error if it can't be set immediately.
Klee> I'm not entirely happy with the future-break command, and
Klee> particularly with its interaction with the save-breakpoints
Klee> mechanism (if you set a breakpoint that is in a shared library
Klee> after shared libraries have been loaded, you have to remember to
Klee> use the future-break command, not the break command).
Doesn't this mean that programs like Insight would be best advised to
*only* set future breakpoints? In that case let's just add the
functionality directly to the existing breakpoint commands.
Tom
next prev parent reply other threads:[~2001-12-05 22:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 10:21 Klee Dienes
2001-12-04 10:26 ` Daniel Jacobowitz
2001-12-04 10:44 ` Klee Dienes
2001-12-05 14:06 ` Tom Tromey [this message]
2001-12-04 11:22 ` Eli Zaretskii
2001-12-04 13:35 ` Klee Dienes
2001-12-05 0:25 ` Eli Zaretskii
2001-12-04 14:48 ` Michael Snyder
2001-12-04 21:11 ` Klee Dienes
2001-12-11 0:28 ` Klee Dienes
2001-12-11 3:55 ` Eli Zaretskii
2001-12-11 8:35 ` Klee Dienes
2001-12-11 9:09 ` Eli Zaretskii
2001-12-11 13:23 ` Klee Dienes
2001-12-12 0:32 ` Eli Zaretskii
2001-12-14 12:45 ` Klee Dienes
2001-12-14 12:50 ` Daniel Jacobowitz
2001-12-18 1:42 ` Klee Dienes
[not found] <1007594419.30359.ezmlm@sources.redhat.com>
2001-12-05 17:39 ` Jim Ingham
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=87d71t8gke.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@apple.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