public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: llewins@raytheon.com To: insight-gnats@sources.redhat.com Subject: insight/202: Error: bad text index "4" Date: Fri, 10 Jan 2003 21:53:00 -0000 [thread overview] Message-ID: <20030110214304.17436.qmail@sources.redhat.com> (raw) >Number: 202 >Category: insight >Synopsis: Error: bad text index "4" >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 10 13:53:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: Lloyd J. Lewins >Release: unknown-1.0 >Organization: >Environment: >Description: When navigating to a source file using the pull down list, I received the following error dialog box. This was repeatable until I deleted all breakpoints. Then the error went away. Dialog box opens" Error: bad text index "4" bad text index "4" while executing "$win tag add $tag $linenum.0 $stop" (object "::.srcwin0.srcwin.container.pane2.childsite.con" method "::SrcTextWin::insertBreakTag" body line 31) invoked from within "insertBreakTag $win $linenum $tag_type" (object "::.srcwin0.srcwin.container.pane2.childsite.con" method "::SrcTextWin::do_bp" body line 90) invoked from within "do_bp $twin $action $linenum $type $bpnum $enabled $thread 0" ("SOURCE" arm line 3) invoked from within "switch $current(mode) { SOURCE { if {[string compare $file $current(filename)] == 0 && $linenum != {}} { do_bp $twin $action $linenum $type..." (object "::.srcwin0.srcwin.container.pane2.childsite.con" method "::SrcTextWin::bp" body line 4) invoked from within "bp create $bpnum $addr $line $file $type $enabled" (object "::.srcwin0.srcwin.container.pane2.childsite.con" method "::SrcTextWin::display_breaks" body line 30) invoked from within "display_breaks" (object "::.srcwin0.srcwin.container.pane2.childsite.con" method "::SrcTextWin::location" body line 69) invoked from within "$twin location $tag $name $funcname $line $addr $pc_addr $lib" (object "::.srcwin0.srcwin" method "::SrcWin::location" body line 60) invoked from within "location BROWSE_TAG [list $val "" $full 0 0 0 {}]" (object "::.srcwin0.srcwin" method "::SrcWin::_name" body line 26) invoked from within "::.srcwin0.srcwin _name .srcwin0.srcwin.container.pane1.childsite.con.name route.cc" (in namespace inscope "::SrcWin" script line 1) invoked from within "namespace inscope ::SrcWin {::.srcwin0.srcwin _name} .srcwin0.srcwin.container.pane1.childsite.con.name route.cc" ("after" script)errorCode is NONE >How-To-Repeat: No idea. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-10 21:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-10 21:53 llewins [this message] 2004-07-31 17:33 Bernhard Walle 2005-04-23 18:03 Insight/202: " mozleron 2005-07-14 8:13 insight/202: " Ruppert 2009-10-09 3:08 kseitz
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=20030110214304.17436.qmail@sources.redhat.com \ --to=llewins@raytheon.com \ --cc=insight-gnats@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: linkBe 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).