From: Nick Roberts <nickrob@snap.net.nz>
To: Jim Ingham <jingham@apple.com>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: 'continue' command problem
Date: Tue, 26 Jun 2007 04:40:00 -0000 [thread overview]
Message-ID: <18048.39066.783422.293969@kahikatea.snap.net.nz> (raw)
In-Reply-To: <D55FFBAC-7B85-40DE-8F71-D373C8A6AA90@apple.com>
Jim Ingham writes:
> At Apple, we also added a "breakpoint-commands" output field to the
> "*stopped - breakpoint-hit" message.
I can see an MI command -break-commands but no output field,
"breakpoint-commands". Which file is it in?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-06-26 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706041421.21962.leonp@plris.com>
2007-06-25 7:02 ` Vladimir Prus
2007-06-25 7:51 ` Nick Roberts
2007-06-25 18:04 ` Jim Ingham
2007-06-26 4:40 ` Nick Roberts [this message]
2007-06-26 18:16 ` Jim Ingham
2007-06-27 0:12 ` Nick Roberts
2007-06-26 7:13 ` 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=18048.39066.783422.293969@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=jingham@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