Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: Avoid decode_objc clobbering current language
Date: Sat, 24 May 2008 08:18:00 -0000	[thread overview]
Message-ID: <20080523183431.GK4080@adacore.com> (raw)
In-Reply-To: <je8wy3d2t8.fsf@sykes.suse.de>

Hi Andreas,

> The problem is that sal_decode_line_1 (here called from
> breakpoint_re_set_one) calls decode_objc, which indirectly calls
> get_selected_frame.  Since the program is just being started there is no
> selected frame yet, thus get_selected_frame called select_frame, which
> re-sets current_language (typically to language_c).  Thus the
> set_language call in breakpoint_re_set_one is useless.

This is an issue that I'm planning to address properly. I had some plans
earlier this year to do it, but then decided to think about it some more.
Basically, the idea is to reduce the use of the current_language to
the minimum, which is use it as the context when the user enters a
command.

It's one of the things that I want to get done around July to September.

> 2008-05-21  Andreas Schwab  <schwab@suse.de>
> 
> 	* linespec.c (decode_objc): Save current language around call to
> 	get_selected_block.

In the meantime, I think that this is reasonable. Eventually when
the change mentioned above gets under way, I will remove your change.
I feel confident that it will not be missed, because I will have to
review all the uses of current_language anyway. I hope I'm not missing
something!

So, if you confirm that this caused no regression, please go ahead and
commit.

-- 
Joel


  reply	other threads:[~2008-05-23 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 19:38 Andreas Schwab
2008-05-24  8:18 ` Joel Brobecker [this message]
2008-05-26 15:48   ` Andreas Schwab

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=20080523183431.GK4080@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@suse.de \
    /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