Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Michael Snyder <msnyder@vmware.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:29:00 -0000	[thread overview]
Message-ID: <201008312029.48109.pedro@codesourcery.com> (raw)
In-Reply-To: <4C7D5397.4000809@vmware.com>

On Tuesday 31 August 2010 20:10:15, Michael Snyder wrote:
> >> 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.

A pointer to it is passed to add_setshow_enum_cmd:

  add_setshow_enum_cmd ("exec-direction", class_run, exec_direction_names,
			&exec_direction, _("Set direction of execution.\n\
Options are 'forward' or 'reverse'."),
			_("Show direction of execution (forward/reverse)."),
			_("Tells gdb whether to execute forward or backward."),
			set_exec_direction_func, show_exec_direction_func,
			&setlist, &showlist);

"-gdb-show exec-direction" does not call the set callback, it prints the command's
control enum value directly.

 (gdb) show exec-direction 
 Forward.
 (gdb) interpreter-exec mi "-gdb-show exec-direction"
 ^done,value="forward"
  (gdb) 

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.

-- 
Pedro Alves


  reply	other threads:[~2010-08-31 19:29 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 [this message]
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=201008312029.48109.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