GDBEventHandler::GDBEventHandler::dispatch errors

GDBEventHandler::GDBEventHandler::dispatch errors

[Alexander Minushkin]

I work around some problems with "Stop" button in insight 6.1 (under cygwin
trying to debug remote target via RDP). And found the error messages in
"Insight Debug" window.
 

(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" 

 

(GDBEventHandler::GDBEventHandler::dispatch) On idle event,
::.srcwin0.srcwin.container.pane2.childsite.con errored:

member function "::GDBEventHandler::idle" is not defined and cannot be
autoloaded

    (object "::.srcwin0.srcwin.container.pane2.childsite.con" method
"::GDBEventHandler::idle" )

    invoked from within

"$w $handler $event" 

 

(GDBEventHandler::GDBEventHandler::dispatch) On set_variable event,
::.srcwin0.srcwin errored:

member function "::GDBEventHandler::set_variable" is not defined and cannot
be autoloaded

    (object "::.srcwin0.srcwin" method "::GDBEventHandler::set_variable" )

    invoked from within

"$w $handler $event"

 

 

Can this errors affect "Stop" button behavior? 

Anyway, how to fix it?

Re: GDBEventHandler::GDBEventHandler::dispatch errors

[Keith Seitz]

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