From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"palves@redhat.com" <palves@redhat.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>
Subject: RE: [PATCH] record: automatically start recording
Date: Thu, 12 May 2016 13:45:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23332C76B6@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <8637pnctbv.fsf@gmail.com>
> -----Original Message-----
> From: Yao Qi [mailto:qiyaoltc@gmail.com]
> Sent: Thursday, May 12, 2016 3:14 PM
> To: Metzger, Markus T <markus.t.metzger@intel.com>
> Cc: gdb-patches@sourceware.org; palves@redhat.com; ak@linux.intel.com;
> jan.kratochvil@redhat.com
> Subject: Re: [PATCH] record: automatically start recording
Hi Yao,
Thanks for your review. I changed the test to use "record full" and moved it
into testsuite/gdb.reverse.
> > Is the added convenience worth a new option or do we want to point users to
> the
> > breakpoint-command solution?
> >
>
> I don't think it can justify adding a option in GDB to do that, but I am
> open to others' thought. If people think it is useful to have such
> option, see my comments below on the patch,
I get such a request once in a while but I'm not sure about this myself.
Let's hear what others think.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2016-05-12 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 14:34 Markus Metzger
2016-05-09 7:47 ` Metzger, Markus T
2016-05-09 16:19 ` Eli Zaretskii
2016-05-10 7:32 ` Metzger, Markus T
2016-05-12 13:14 ` Yao Qi
2016-05-12 13:45 ` Metzger, Markus T [this message]
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=A78C989F6D9628469189715575E55B23332C76B6@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=ak@linux.intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).