From: Ruppert <dieter_ruppert@siemens.com>
To: insight@sources.redhat.com
Cc: dieter_ruppert@siemens.com
Subject: Re: Unable to restore previously selected frame: Observations
Date: Wed, 04 Dec 2002 04:42:00 -0000 [thread overview]
Message-ID: <200212041242.gB4CgfQ21698@haiti.swb.siemens.de> (raw)
Hi,
Andrew Cagney wrote:
...
> I suspect it's insight@. Switching list back :-)
>
>
> > about two weeks ago I posted the following note to insight@sorces.redhat.com.
> > It deals with a bogus "Unable to restore previously selected frame" warning
> > which seems to occur randomly when a function call is made from the
> > gdb/insight console.
> >
> > I found one reason for this; and because it is more a gdb issue than a
> > insight issue I thought these observations might be useful:
>
> Can you try reproducing this with more up-to-date sources (preferably
> those from the mainline). See:
>
> ftp://sources.redhat.com/pub/gdb/snapshots/current/
>
> The frame code is currently undergoing ongoing radical reform.
> Consequently, this problem may or may not still be present. The global
> variable `selected_frame_level' that you refered to, for instance, has gone.
>
Sorry for the delay. I just tried insight+dejagnu-20021129, and there
the problem is indeed gone. Thus, no need to worry about this.
Thanks for the hint!
Best Regards
D.Ruppert
ru@swb.siemens.de
next reply other threads:[~2002-12-04 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 4:42 Ruppert [this message]
2002-12-04 8:56 ` Andrew Cagney
[not found] <200211131719.gADHJYu14688@haiti.swb.siemens.de>
2002-11-28 20:15 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 7:45 Ruppert
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=200212041242.gB4CgfQ21698@haiti.swb.siemens.de \
--to=dieter_ruppert@siemens.com \
--cc=insight@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).