insight/202: Error: bad text index "4"

insight/202: Error: bad text index "4"

[llewins]

>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:

Re: insight/202: Error: bad text index "4"

[kseitz]

Synopsis: Error: bad text index "4"

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Fri Oct  9 03:08:54 2009
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->closed
State-Changed-By: kseitz
State-Changed-When: Fri Oct  9 03:08:54 2009
State-Changed-Why:
    After [cough] many years, I think I finally figured out how to reproduce this. See http://sources.redhat.com/ml/insight/2009-q4/msg00001.html for an explanation. I don't know about the other suggestion in  dieter_ruppert@siemens.com's response, but I'm not sure it is necessary. I guess in five more years, I'll figure that one out, too! 1/2 :-)

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=202

Re: insight/202: Error: bad text index "4"

[Ruppert]

The following reply was made to PR insight/202; it has been noted by GNATS.

From: Ruppert <dieter_ruppert@siemens.com>
To: insight-gnats@sources.redhat.com
Cc:  
Subject: Re: insight/202: Error: bad text index "4"
Date: Thu, 14 Jul 2005 10:06:08 +0200

 This is a simple bug in srctextwin.itb; the linenumber is missing from a 
 tag. Also, to be safe, it is better to create the tag if it is not 
 available.
 
 A patch for srctextwin.itb (relative to 6.1) fixes this:
 
 *** srctextwin.itb.orig Thu Jul 14 09:53:48 2005
 --- srctextwin.itb      Thu Jul 14 10:01:28 2005
 ***************
 *** 1378,1384 ****
        set other_tag [lindex $tag_list \
                       [lsearch -glob $tag_list {*[bt]p_tag}]]
        if {$other_tag == ""} {
 !       set stop 4
        } else {
          set stop [lindex [$win tag nextrange $other_tag \
                            $linenum.0 "$linenum.0 lineend"] 1]
 --- 1378,1384 ----
        set other_tag [lindex $tag_list \
                       [lsearch -glob $tag_list {*[bt]p_tag}]]
        if {$other_tag == ""} {
 !       set stop $linenum.4
        } else {
          set stop [lindex [$win tag nextrange $other_tag \
                            $linenum.0 "$linenum.0 lineend"] 1]
 ***************
 *** 1385,1392 ****
        }
 
        $win tag add $tag $linenum.0 $stop
 -     $win image configure $linenum.0 -image $break_images($img_name)
 
      }
    }
 
 --- 1385,1399 ----
        }
 
        $win tag add $tag $linenum.0 $stop
 
 +     # create tag if missing, otherwise: configure
 +
 +     if {$other_tag == ""} {
 +        $win image create $linenum.0 -image $break_images($img_name)
 +     } else {
 +        $win image configure $linenum.0 -image $break_images($img_name)
 +     }
 +
      }
    }
 
 

Re: Insight/202: Error: bad text index "4"

[mozleron]

The following reply was made to PR insight/202; it has been noted by GNATS.

From: mozleron@drizzle.com
To: insight-gnats@sources.redhat.com
Cc:  
Subject: Re: Insight/202: Error: bad text index "4"
Date: Sat, 23 Apr 2005 11:19:20 -0700 (PDT)

 I was experiencing this error, and after reading through the stack trace,
 i remembered that i had put a breakpoint at line 31 in my code.  I noticed
 that the bug report also showed a break point at line 31.  I am not sure
 if this is related, but it seems odd.  In any case, i cleared all
 breakpoints, and the error message stopped coming up.  Since my code has
 since changed, i wsa unable to put a breakpoint back in at Line 31, so the
 error has not since re-appeared.
 I am not entirely sure which version of Insight i am using as i downloaded
 it as a package update for DevC++.  It shows as version 1.0 in the DevC++
 Package manager with a source site of http://sources.redhat.com/insight/.
 
 

Re: insight/202: Error: bad text index "4"

[Bernhard Walle]

The following reply was made to PR insight/202; it has been noted by GNATS.

From: Bernhard Walle <Bernhard.Walle@gmx.de>
To: insight-gnats@sources.redhat.com
Cc:  
Subject: Re: insight/202: Error: bad text index "4"
Date: Sat, 31 Jul 2004 19:32:25 +0200

 I have the same problem here. I use Insight 6.1.
 The bug should be fixed in my opinion.