From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26081 invoked by alias); 9 Feb 2005 19:45:35 -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 25968 invoked from network); 9 Feb 2005 19:45:30 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 9 Feb 2005 19:45:30 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j19JjUai030514 for ; Wed, 9 Feb 2005 14:45:30 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j19JjPO02734; Wed, 9 Feb 2005 14:45:25 -0500 Received: from localhost.localdomain (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j19JjOgi019281; Wed, 9 Feb 2005 14:45:24 -0500 Subject: Re: GDBEventHandler::GDBEventHandler::dispatch errors From: Keith Seitz To: Alexander Minushkin Cc: insight@sources.redhat.com In-Reply-To: References: Content-Type: text/plain Date: Wed, 09 Feb 2005 19:45:00 -0000 Message-Id: <1107978323.5118.10.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q1/txt/msg00037.txt.bz2 On Wed, 2005-02-09 at 14:03 +0300, Alexander Minushkin wrote: > (GDBEventHandler::GDBEventHandler::dispatch) On busy event, > ::.srcwin0.srcwin.container.pane2.childsite.con errored: > > member function "::GDBEventHandler::busy" is not defined and cannot be > autoloaded > > (object "::.srcwin0.srcwin.container.pane2.childsite.con" method > "::GDBEventHandler::busy" ) > > invoked from within > > "$w $handler $event" [snip] > Can this errors affect "Stop" button behavior? This is very unusual, but it should not affect the stop button's behavior. All of these errors are "caught" in GDBEventHandler::dispatch: # invoke event handlers foreach w [itcl_info objects -isa GDBEventHandler] { dbug I "posting event \"$handler\" to \"$w\"" if {[catch {$w $handler $event}]} { dbug E "On $handler event, $w errored:\n$::errorInfo" } } FWIW, I don't think the stop button will work with RDP (or almost any remote target, for that matter). To know for sure, try firing up command-line gdb and then interrupting your running inferior with ^C (control-c). If this successfully interrupts the target, you've found a bug. > Anyway, how to fix it? I am mesmerized by these messages. I cannot even fathom how this could occur. As you can see from the code above, GDBEventHandler::dispatch gets a list of classes that inherit from GDBEventHandler. It then loops through these windows, invoking the requested handler. The errors suggest that GDBEventHandler::busy (and others) is "undefined" for the class it is attempting to call it on. Which doesn't make sense, of course, since these undefined methods are inherited from GDBWin (which inherits them from GDBEventHandler). I've checked cvs HEAD, and these problems do not exist. Is it possible that the inheritance was lost by someone modifying srctextwin.itb or similar? Missing files or something? I wish I had more concrete advice for you, but I'm really puzzled by this. Sorry. Keith