From: Jim Ingham <jingham@apple.com>
To: Bob Rossi <bob_rossi@cox.net>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: MI and pending breakpoints
Date: Wed, 15 Mar 2006 16:34:00 -0000 [thread overview]
Message-ID: <01D1CA11-FB79-43C6-AD3F-DC4C3D49B465@apple.com> (raw)
In-Reply-To: <20060315162122.GA30980@brasko.net>
On Mar 15, 2006, at 8:21 AM, Bob Rossi wrote:
> On Wed, Mar 15, 2006 at 08:19:59AM -0800, Jim Ingham wrote:
>> You need to set the gdb variable "pending" to "on" before setting the
>> breakpoint. Since this is kind of a pain, we added a "-f" option
>> to -
>> break-insert that will do this for you wrapped around the breakpoint
>> setting ("-f" because this feature was called "future-break" in the
>> NeXT gdb many years ago.)
>>
>> It's also arguable that for -break-insert you ALWAYS want "pending"
>> to be "on".
>
> That's how annotate=2 works. However, I think GDB should query the
> user
> the same way it does from the CLI. It's wierd when people start
> using my
> front end and ask why it behaves differently than the CLI.
Not sure I agree with this. AFAICT, the main reason for asking the
user is that you can easily mis-type a file:line spec, and it's good
to have the CLI tell you this didn't set so you can check your
spelling. But this should not be possible for the most common type
of breakpoint in a UI, which is clicking in the gutter of an editor
window.
I think having the UI query would be disruptive...
Jim
next prev parent reply other threads:[~2006-03-15 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 14:22 Vladimir Prus
2006-03-15 16:21 ` Jim Ingham
2006-03-15 16:30 ` Bob Rossi
2006-03-15 16:34 ` Jim Ingham [this message]
2006-03-15 16:48 ` Bob Rossi
2006-03-15 23:18 ` Jim Ingham
2006-03-16 15:36 ` Nick Roberts
2006-03-15 16:31 ` Vladimir Prus
2006-03-15 16:39 ` Jim Ingham
2006-03-17 10:35 ` Vladimir Prus
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=01D1CA11-FB79-43C6-AD3F-DC4C3D49B465@apple.com \
--to=jingham@apple.com \
--cc=bob_rossi@cox.net \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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