public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Alexander Minushkin <aminushk@rfmd.com>
Cc: insight@sources.redhat.com
Subject: Re: GDBEventHandler::GDBEventHandler::dispatch errors
Date: Wed, 09 Feb 2005 19:45:00 -0000	[thread overview]
Message-ID: <1107978323.5118.10.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <MAIL3hGD1XyCTr9rf3y000108d2@mail3.internal.rfmd.com>

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

      reply	other threads:[~2005-02-09 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 11:04 Alexander Minushkin
2005-02-09 19:45 ` Keith Seitz [this message]

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=1107978323.5118.10.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=aminushk@rfmd.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).