From: Vladimir Prus <vladimir@codesourcery.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Implement -break-commands
Date: Mon, 27 Jul 2009 16:17:00 -0000 [thread overview]
Message-ID: <200907272000.38076.vladimir@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA07C69282@ecamlmw720.eamcs.ericsson.se>
On Monday 27 July 2009 Marc Khouzam wrote:
> > -----Original Message-----
> > From: gdb-patches-owner@sourceware.org
> > [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus
> > Sent: Monday, July 27, 2009 5:03 AM
> > To: gdb-patches@sources.redhat.com
> > Subject: [RFA] Implement -break-commands
> >
> >
> > The below patches implement MI -break-commands. As the name implies,
> > it's the same as CLI 'commands'. There are two patches: one
> > refactors CLI 'commands' for easier reuse, and the second actually
> > adds -break-commands. The patches mostly were derived from Apple
> > branch, and then adjusted for CVS HEAD. One functional change I've
> > made is that '-break-commands <number>' does not report the list
> > of currently set commands -- since -break-info already prints his
> > information, it does not seem necessary to add another way. I've
> > also added a test and docs.
>
> Nice addition.
>
> >
> > The parts of this patch that are not MI are:
> > 1. Slight refactoring of cli/cli-script.c
> > 2. Slight refactoring of breakpoint.c
> >
> > I'd appreciate if somebody could review them.
> >
> > Eli, there's also doc change here, comments appreciated.
>
> I noticed the example in the doc is missing the breakpoint number:
>
> > +-break-command "print v" "continue"
>
> Unless it is optional?
It's a doc bug -- thanks for noticing. I've fixed it in my patch tree.
- Volodya
next prev parent reply other threads:[~2009-07-27 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 16:00 Vladimir Prus
2009-07-27 16:08 ` Marc Khouzam
2009-07-27 16:17 ` Vladimir Prus [this message]
2009-07-27 18:49 ` Tom Tromey
2009-07-27 17:38 ` Vladimir Prus
2009-07-29 21:08 ` Tom Tromey
2009-07-30 7:54 ` Vladimir Prus
2009-07-30 16:57 ` Tom Tromey
2009-08-03 12:40 ` Vladimir Prus
2009-07-30 21:22 ` Eli Zaretskii
2009-08-03 12:42 ` Vladimir Prus
2009-08-03 18:22 ` Eli Zaretskii
2009-07-27 18:56 ` Eli Zaretskii
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=200907272000.38076.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=marc.khouzam@ericsson.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