From: Tom Tromey <tromey@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Fix for gdb.parameter('architecture') returning empty string
Date: Fri, 02 Nov 2012 19:52:00 -0000 [thread overview]
Message-ID: <87hap7ok98.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAGyQ6gxnp+2_yLGiqj7x9ctQ-HTBmMNPU=nRUC5y2UBYWfwbgQ@mail.gmail.com> (Siva Chandra's message of "Fri, 2 Nov 2012 11:45:49 -0700")
>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:
Tom> I think this just means that "show architecture" will now show incorrect
Tom> results, though.
Siva> This is for my understanding: Can you give an example where this can
Siva> give incorrect results. Is it only for the case when the arch can
Siva> change from frame to frame? I have tested for all cases that I could
Siva> think of and it seems fine.
Yeah, if two frames have different architectures and the user does "show
arch" in each one.
I could be wrong. I don't have a setup like this to actually test it.
I just didn't see what notifies the architecture-changed observer in
this scenario.
Similarly, I think if the inferior starts or exits, and it has a
different architecture from the target_gdbarch, then observer will not
be notified, yielding wrong results.
Siva> For now, I have been using gdb.execute("show architecture",
Siva> to_string=True) and getting the value from the resulting string. I am
Siva> trying to tidy that up by using gdb.parameter(...). And, for my work,
Siva> exposing arch from frames will work as I need the arch during an
Siva> active frame only. I see two items here then:
Siva> 1. Fix gdb.parameter by the way of using methods on CLI objects.
Siva> 2. Expose current frame arch through the gdb.Frame class.
Siva> Do they seem reasonable?
I think so.
Tom
next prev parent reply other threads:[~2012-11-02 19:52 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
2012-11-02 16:59 ` Tom Tromey
2012-11-02 18:45 ` Siva Chandra
2012-11-02 19:52 ` Tom Tromey [this message]
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=87hap7ok98.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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