From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: Different output from -gdb-show than show
Date: Tue, 31 Aug 2010 19:10:00 -0000 [thread overview]
Message-ID: <4C7D5397.4000809@vmware.com> (raw)
In-Reply-To: <201008312007.57425.pedro@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Pedro Alves wrote:
> On Tuesday 31 August 2010 20:03:06, Michael Snyder wrote:
>> Pedro Alves wrote:
>>> On Tuesday 31 August 2010 19:33:17, Michael Snyder wrote:
>>>
>>>> Would this be suitable?
>>> You also need to reset exec_direction back from execution_direction
>>> in set_exec_direction_func. The set command callbacks are called _after_
>>> their controlled variable has already been changed. See
>>> infrun.c:set_non_stop, for example.
>>>
>> Hmmm, but "exec_direction" doesn't actually seem to be used anywhere.
>>
>> I did try this patch, and after failing to set "reverse", it
>> still shows "Forward".
>>
>> What am I missing?
>
> That "-gdb-show exec-direction" reads from exec_direction. See
> Marc's original bug report upthread. :-)
>
I don't see how, since it's a static variable and I've looked at
every local reference to it.
But anyway, here's a new patch:
[-- Attachment #2: infrun.txt --]
[-- Type: text/plain, Size: 731 bytes --]
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.
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.445
diff -u -p -r1.445 infrun.c
--- infrun.c 1 Jul 2010 15:36:15 -0000 1.445
+++ infrun.c 31 Aug 2010 19:09:07 -0000
@@ -6436,6 +6436,11 @@ set_exec_direction_func (char *args, int
else if (!strcmp (exec_direction, exec_reverse))
execution_direction = EXEC_REVERSE;
}
+ else
+ {
+ exec_direction = exec_forward;
+ error (_("Target does not support this operation."));
+ }
}
static void
next prev parent reply other threads:[~2010-08-31 19:10 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 [this message]
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
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=4C7D5397.4000809@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=pedro@codesourcery.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