This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [rfc] btrace: change record instruction-history /m


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]