From: Marc Khouzam <marc.khouzam@ericsson.com>
To: Pedro Alves <palves@redhat.com>,
Markus Metzger <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"dje@google.com" <dje@google.com>,
Simon Marchi <simon.marchi@ericsson.com>
Subject: RE: [rfc] btrace: change record instruction-history /m
Date: Wed, 19 Aug 2015 14:45:00 -0000 [thread overview]
Message-ID: <E59706EF8DB1D147B15BECA3322E4BDC228549F4@eusaamb103.ericsson.se> (raw)
In-Reply-To: <55D347E7.2080703@redhat.com>
> From: gdb-patches-owner@sourceware.org [gdb-patches-owner@sourceware.org] on behalf of Pedro Alves [palves@redhat.com]
> Sent: August 18, 2015 10:57 AM
> To: Markus Metzger
> Cc: gdb-patches@sourceware.org; dje@google.com; Simon Marchi
> Subject: Re: [rfc] btrace: change record instruction-history /m
>
> On 08/14/2015 12:37 PM, Markus Metzger wrote:
> > I don't think that there is an MI consumer of "record instruction-history"
> > and I have no idea if and how this might affect MI.
>
> I think Eclipse has support for reverse debugging, but AFAIK, there
> are no MI commands for getting at the instruction history.
> I see that it issues the CLI "record" and "record stop" stop commands, but
> that's it, AFAICS. Unless it plays tricks with CLI commands that are
> escaping my greps, it shouldn't be affected.
You're right, all Eclipse uses now is "record" and "record stop" which we use
in CLI form (there is no MI version to my knowledge).
We also use the MI events "=record-started" and "=record-stopped".
Marc
prev parent reply other threads:[~2015-08-19 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 11:37 Markus Metzger
2015-08-14 13:45 ` Eli Zaretskii
2015-08-14 17:06 ` Doug Evans
2015-08-14 20:32 ` Eli Zaretskii
2015-08-17 7:16 ` Metzger, Markus T
2015-08-17 15:10 ` Eli Zaretskii
2015-08-18 6:30 ` Metzger, Markus T
2015-08-18 14:22 ` Eli Zaretskii
2015-08-14 17:02 ` Doug Evans
2015-08-14 17:44 ` Doug Evans
2015-08-17 7:23 ` Metzger, Markus T
2015-08-18 14:57 ` Pedro Alves
2015-08-19 14:45 ` Marc Khouzam [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=E59706EF8DB1D147B15BECA3322E4BDC228549F4@eusaamb103.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=simon.marchi@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