From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: GDB Error: bad window path name ".watchwin0"
Date: Thu, 30 Apr 2009 19:50:00 -0000 [thread overview]
Message-ID: <gtcvdh$oec$1@ger.gmane.org> (raw)
If I have Insight running for a while and do enough watches (just
looking at a single simple variable at a time) I get the pop up error
GDB Error: bad window path name ".watchwin0". If I press the "Stack
Trace" button I see:
bad window path name ".watchwin0"
while executing
"raise $_top"
(object "::.watchwin0.watchwin" method "::ManagedWin::reveal" body
line 5)
invoked from within
"$obj reveal"
(procedure "::ManagedWin::_open" body line 10)
invoked from within
"_open WatchWin"
("eval" body line 1)
invoked from within
"eval _open $class $args"
(procedure "::ManagedWin::open" body line 3)
invoked from within
"ManagedWin::open WatchWin"
(object "::.srcwin0.srcwin.container.pane2.childsite.con" method
"::SrcTextWin::addToWatch" body line 2)
invoked from within
"::.srcwin0.srcwin.container.pane2.childsite.con addToWatch Size"
invoked from within
".srcwin0.srcwin.container.pane2.childsite.con.src_menu invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tk::MenuInvoke" line 47)
invoked from within
"tk::MenuInvoke .srcwin0.srcwin.container.pane2.childsite.con.src_menu 1
"
(command bound to event)errorCode is NONE
I am unable to do further watches w/o restarting insight. This occurs on
V6.8 w/linux fc8 and I think I have seen it with newer snapshots too.
-gene
reply other threads:[~2009-04-30 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gtcvdh$oec$1@ger.gmane.org' \
--to=gds@chartertn.net \
--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).