From: Pedro Alves <pedro@codesourcery.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'Michael Snyder'" <msnyder@vmware.com>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: Re: Different output from -gdb-show than show
Date: Tue, 31 Aug 2010 20:03:00 -0000 [thread overview]
Message-ID: <201008312102.50990.pedro@codesourcery.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5717034C63@EUSAACMS0703.eamcs.ericsson.se>
On Tuesday 31 August 2010 20:39:51, Marc Khouzam wrote:
> > -----Original Message-----
> > From: gdb-owner@sourceware.org
> > [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder
> > Sent: Tuesday, August 31, 2010 3:33 PM
> > To: Pedro Alves
> > Cc: gdb@sourceware.org; Marc Khouzam
> > Subject: Re: Different output from -gdb-show than show
> >
> > Pedro Alves wrote:
> >
> > > Note "Forward." vs "forward".
> > >
> > >> 2010-08-31 Michael Snyder
> > <msnyder@msnyder-server.eng.vmware.com>
> > >>
> > >> * infrun.c (set_exec_direction_func): Error out if
> > target does not
> > >> support reverse execution.
> > >
> > > Okay.
> >
> > Thanks, applied to trunk and branch.
>
> Thanks guys!
>
> Here is what I'm planning to do to see if a target supports reverse
> execution:
>
> -gdb-set exec-direction reverse
> show exec-direction
> -gdb-set exec-direction forward
>
> If the 'show' command shows "Reverse", I'll know that the target
> supports reverse execution. (I have to do it like this because
> I also want it to work for 7.0 and 7.1)
>
> That is the only thing I found that gave me that info without
> side-effects. Makes sense?
Yes. You may want to issue an "-gdb-set exec-direction forward"
upfront to clean up any stale state from a previous run/target
as well... Also, it may wreck havoc in non-stop if the target is
already executing... I think listing support for reverse
in "-list-target-features" would be nice?
--
Pedro Alves
next prev parent reply other threads:[~2010-08-31 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 15:03 Marc Khouzam
2010-08-31 15:29 ` Pedro Alves
2010-08-31 18:33 ` Michael Snyder
2010-08-31 18:37 ` Marc Khouzam
2010-08-31 18:41 ` Pedro Alves
2010-08-31 19:03 ` Michael Snyder
2010-08-31 19:08 ` Pedro Alves
2010-08-31 19:10 ` Michael Snyder
2010-08-31 19:29 ` Pedro Alves
2010-08-31 19:32 ` Michael Snyder
2010-08-31 19:40 ` Marc Khouzam
2010-08-31 20:03 ` Pedro Alves [this message]
2010-08-31 20:11 ` Marc Khouzam
2010-08-31 20:27 ` Pedro Alves
2010-09-01 15:37 ` Marc Khouzam
2010-08-31 19:39 ` Tom Tromey
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=201008312102.50990.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.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