From: Siva Chandra <sivachandra@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Fix for gdb.parameter('architecture') returning empty string
Date: Fri, 02 Nov 2012 13:44:00 -0000 [thread overview]
Message-ID: <CAGyQ6gwrvdUmUzmxbt89EFvmbSwau9Pw_vGBShwcOuw0TJheZg@mail.gmail.com> (raw)
In-Reply-To: <87y5ilqdoz.fsf@fleche.redhat.com>
On Thu, Nov 1, 2012 at 1:18 PM, Tom Tromey <tromey@redhat.com> wrote:
> I'm not certain that this patch is correct. Also I tend to think (but
> of course I am willing to be convinced otherwise) that a different
> direction would be preferable.
>
> Siva> +static void
> Siva> +on_architecture_change (struct gdbarch *arch)
> Siva> +{
> Siva> + architecture_string = gdbarch_bfd_arch_info (arch)->printable_name;
> Siva> + set_endian_string (arch);
> Siva> +}
>
> Siva> + observer_attach_architecture_changed (on_architecture_change);
>
> I suspect this means that gdb.parameter('architecture') will not always
> show the same result as "show architecture".
I do not understand this completely. In my patch, show_architecture
only prints 'architecture_string'. Hence,
gdb.parameter('architecture') and "show architecture" should always
show the same result. Did I miss something?
> Right now, in the auto case show_architecture will call
> get_current_arch:
>
> struct gdbarch *
> get_current_arch (void)
> {
> if (has_stack_frames ())
> return get_frame_arch (get_selected_frame (NULL));
> else
> return target_gdbarch;
> }
>
> But from what I can tell, the architecture-change observer is not
> notified in every situation that might cause that function to return a
> different result.
Pardon my ignorance here, does target arch change between frames?
> I think a better approach might be to address the problem of "auto" gdb
> parameters more globally. For example, we could add a method to the
> appropriate CLI object so that the Python could call this to get the
> correct current value.
Do you mean that the CLI object should have a method (which can
evaluate the property value on the go), rather than a property like
'architecture_string' and 'endian_string'? If yes, do you envision
that Python make use of the method if it exists, otherwise use the
property?
Thanks,
Siva Chandra
next prev parent reply other threads:[~2012-11-02 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 23:43 Siva Chandra
2012-10-14 7:53 ` Andreas Schwab
2012-10-14 8:37 ` Siva Chandra
2012-10-22 7:16 ` Siva Chandra
2012-11-01 20:19 ` Tom Tromey
2012-11-02 13:44 ` Siva Chandra [this message]
2012-11-02 16:59 ` Tom Tromey
2012-11-02 18:45 ` Siva Chandra
2012-11-02 19:52 ` Tom Tromey
2012-11-05 10:39 ` Phil Muldoon
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=CAGyQ6gwrvdUmUzmxbt89EFvmbSwau9Pw_vGBShwcOuw0TJheZg@mail.gmail.com \
--to=sivachandra@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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