From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"tromey@redhat.com" <tromey@redhat.com>
Subject: Re: PR8554: New command to save breakpoints to a file
Date: Thu, 15 Apr 2010 17:52:00 -0000 [thread overview]
Message-ID: <4BC7523B.6010708@vmware.com> (raw)
In-Reply-To: <201004121914.44401.pedro@codesourcery.com>
Pedro Alves wrote:
> On Friday 09 April 2010 18:23:31, Pedro Alves wrote:
>> On Friday 09 April 2010 17:17:31, Tom Tromey wrote:
>>>>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>>> Pedro> (I finished this instead of dumping it.)
>>>
>>> Thanks. I do like this approach.
>>>
>>> Pedro> Add a new save-breakpoints command to save breakpoint definitions
>>> Pedro> to a file.
>>>
>>> I'd personally prefer "save breakpoints", with a space, and make
>>> save-tracepoints a deprecated alias for "save tracepoints". What do you
>>> (and others) think of this? I tend to like simple commands with spaces,
>>> especially when a subcommand comes along.
>> Fine with me.
>
> Done now.
What about watchpoints? Do we get all the context info right?
next prev parent reply other threads:[~2010-04-15 17:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 2:41 Pedro Alves
2010-04-09 16:17 ` Tom Tromey
2010-04-09 17:23 ` Pedro Alves
2010-04-10 4:10 ` Sergio Durigan Junior
2010-04-12 18:15 ` Pedro Alves
2010-04-15 17:52 ` Michael Snyder [this message]
2010-04-15 18:27 ` Pedro Alves
2010-04-15 18:46 ` Michael Snyder
2010-04-15 18:53 ` Pedro Alves
2010-04-15 18:58 ` Michael Snyder
2010-04-15 19:58 ` Pedro Alves
2010-04-15 22:49 ` Michael Snyder
2010-04-15 22:52 ` Michael Snyder
2010-04-15 22:58 ` Michael Snyder
2010-04-15 23:05 ` Pedro Alves
2010-04-15 23:15 ` Michael Snyder
2010-04-15 23:25 ` Pedro Alves
2010-05-05 8:28 ` Hui Zhu
2010-04-15 23:14 ` Michael Snyder
2010-04-15 23:20 ` Pedro Alves
2010-04-15 23:01 ` Pedro Alves
2010-04-15 18:59 ` Stan Shebs
2010-04-15 19:10 ` Pedro Alves
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=4BC7523B.6010708@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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