From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Bob Rossi <bob_rossi@cox.net>, gdb@sourceware.org
Subject: Re: [MI] -break-delete with several breakpoints
Date: Sun, 27 Apr 2008 13:56:00 -0000 [thread overview]
Message-ID: <18451.46621.12013.690042@kahikatea.snap.net.nz> (raw)
Message-ID: <20080427135600.1emA1khlbRTh4pQJUHZmTEfias4MDwmt9gMDHKca3tc@z> (raw)
In-Reply-To: <200804270222.50020.vladimir@codesourcery.com>
> > > The only case I can think that would be nice is something like,
> > > -break-disable -all
> >
> > -break-disable with no argument will already do this as it just executes
> > the CLI command "disable".
>
> Which is not guaranteed to be the case in future. That's why I'm trying to
> figure what is desired behaviour is.
Leave it as it is? It doesn't really bother me as these commands don't
create any output and Emacs needs to work with the CLI commands in the GUD
buffer anyway.
I think more important than the input syntax is some kind of output as I
suggested in:
http://sourceware.org/ml/gdb-patches/2008-04/msg00377.html
And it should work with CLI commands too, i.e., through event notification.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-27 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 21:28 Vladimir Prus
2008-04-26 22:23 ` Bob Rossi
2008-04-27 4:26 ` Nick Roberts
2008-04-27 4:26 ` Vladimir Prus
2008-04-27 6:25 ` Nick Roberts [this message]
2008-04-27 13:56 ` Nick Roberts
2008-04-28 17:55 ` André Pönitz
2008-04-29 18:51 ` Michael Snyder
2008-05-03 6:56 FW: " Bjarke Viksoe
2008-05-03 14:25 ` Daniel Jacobowitz
2008-05-03 15:23 ` Bjarke Viksoe
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=18451.46621.12013.690042@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob_rossi@cox.net \
--cc=gdb@sourceware.org \
--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