From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11024 invoked by alias); 4 Dec 2002 12:42:49 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 11017 invoked from network); 4 Dec 2002 12:42:46 -0000 Received: from unknown (HELO lizzard.sbs.de) (194.138.37.39) by sources.redhat.com with SMTP; 4 Dec 2002 12:42:46 -0000 Received: from mail.fth.sbs.de (mail.fth.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.11.6/8.11.6) with ESMTP id gB4Cgj128341 for ; Wed, 4 Dec 2002 13:42:45 +0100 (MET) Received: from nsprim.swb.siemens.de (nsprim.swb.siemens.de [141.73.80.3]) by mail.fth.sbs.de (8.11.6/8.11.6) with ESMTP id gB4CghZ25888 for ; Wed, 4 Dec 2002 13:42:43 +0100 (MET) Received: from haiti.swb.siemens.de (haiti.swb.siemens.de [141.73.80.6]) by nsprim.swb.siemens.de (8.9.1/8.9.1) with ESMTP id NAA22105 for ; Wed, 4 Dec 2002 13:42:41 +0100 (MET) Received: from sylt (sylt [141.19.4.2]) by haiti.swb.siemens.de (8.10.2+Sun/8.10.2) with SMTP id gB4CgfQ21698; Wed, 4 Dec 2002 13:42:41 +0100 (MET) Message-Id: <200212041242.gB4CgfQ21698@haiti.swb.siemens.de> Date: Wed, 04 Dec 2002 04:42:00 -0000 From: Ruppert Reply-To: Ruppert Subject: Re: Unable to restore previously selected frame: Observations To: insight@sources.redhat.com Cc: dieter_ruppert@siemens.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: AyVB2DczrDAgjJ6PscvW8Q== X-SW-Source: 2002-q4/txt/msg00156.txt.bz2 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