From: Daniel Jacobowitz <drow@false.org>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: Re: MI *stopped versus silent breakpoint
Date: Thu, 05 Feb 2009 22:42:00 -0000 [thread overview]
Message-ID: <20090205224242.GA1306@caradoc.them.org> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BF6C@ecamlmw720.eamcs.ericsson.se>
On Thu, Feb 05, 2009 at 05:29:26PM -0500, Marc Khouzam wrote:
> Hi,
>
> I'm curious as to the motivation behind silent breakpoints.
> I'm trying to understand why a frontend would need to know
> of a silent bp hit, but not a user?
> For instance, in async mode, if a silent bp is used,
> how would the user ever know it is hit? And if the user
> need not know, why would a frontend?
Mostly, they're for commands lists that automatically resume. For
instance, if you want to increment a counter every time a breakpoint
is hit, you might mark it as:
silent
commands
set $i++
continue
end
What to do with MI notifications in this case, I don't know...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-05 22:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 15:41 Marc Khouzam
2009-02-03 5:36 ` teawater
2009-02-03 11:49 ` Marc Khouzam
2009-02-05 8:10 ` teawater
2009-02-05 9:25 ` Vladimir Prus
2009-02-05 9:30 ` teawater
2009-02-05 9:35 ` Vladimir Prus
2009-02-05 15:43 ` teawater
2009-02-05 22:30 ` Marc Khouzam
2009-02-05 22:42 ` Daniel Jacobowitz [this message]
2009-02-05 23:25 ` Marc Khouzam
2009-02-06 2:30 ` Daniel Jacobowitz
2009-02-06 3:30 ` teawater
2009-02-06 7:48 ` Marc Khouzam
2009-02-06 10:42 ` 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=20090205224242.GA1306@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=marc.khouzam@ericsson.com \
--cc=vladimir@codesourcery.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