Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] wrong language used when re-setting breakpoint
Date: Tue, 18 Sep 2012 19:16:00 -0000	[thread overview]
Message-ID: <87obl3w39p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120918185535.GG3276@adacore.com> (Joel Brobecker's message of	"Tue, 18 Sep 2012 11:55:35 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> In the meantime, I have found the source of the language switch, and
Joel> I know why you're not seeing it.  There is a function called
Joel> ada-lang.c:add_symbols_from_enclosing_procs which is empty in the
Joel> official tree, but starts with the following code in our tree:
Joel>    frame = deprecated_safe_get_selected_frame ();

Ah, I see.

Joel> Perhaps we (AdaCore) should also do something to avoid the
Joel> language-switch side-effect, but I am hesitant to do anything,
Joel> because I'm thinking I might affect something else later on.

I don't really know the Ada code well enough to comment.
The current code you have sounds tricky, maybe too tricky.

I wouldn't mind pushing linespec to be more fully parameterized.
However, this is maybe non-trivial if it calls out into other parts of
gdb.

I do see that linespec itself takes care to restore current_language in
a similar scenario; see get_search_block.  But I wonder whether this can
have the effect of accidentally dropping a language switch.

Tom


      reply	other threads:[~2012-09-18 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  0:40 Joel Brobecker
2012-09-18 14:52 ` Tom Tromey
2012-09-18 15:06   ` Joel Brobecker
2012-09-18 17:36     ` Tom Tromey
2012-09-18 17:47     ` Tom Tromey
2012-09-18 18:18       ` Joel Brobecker
2012-09-18 18:26         ` Tom Tromey
2012-09-18 18:55           ` Joel Brobecker
2012-09-18 19:16             ` Tom Tromey [this message]

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=87obl3w39p.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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