This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 243556 - StringIndexOutOfBoundsException: String index out of range: 51
Summary: StringIndexOutOfBoundsException: String index out of range: 51
Status: RESOLVED DUPLICATE of bug 244472
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: henk89
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-04 11:13 UTC by Exceptions Reporter
Modified: 2014-05-15 09:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 208921


Attachments
stacktrace (1.43 KB, text/plain)
2014-04-04 11:13 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2014-04-04 11:13:53 UTC
This issue was reported manually by alexvsimon.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 20140311-f5abf3ff69e2)
VM: OpenJDK 64-Bit Server VM, 24.45-b08, OpenJDK Runtime Environment, 1.7.0_51-b00
OS: Linux

User Comments:
GUEST: Closed a debug session.




Stacktrace: 
java.lang.StringIndexOutOfBoundsException: String index out of range: 51
   at java.lang.AbstractStringBuilder.getChars(AbstractStringBuilder.java:353)
   at java.lang.StringBuilder.getChars(StringBuilder.java:72)
   at org.netbeans.modules.cnd.debugger.gdb2.Tap.processCharFromGdb(Tap.java:286)
   at org.netbeans.modules.cnd.debugger.gdb2.Tap.putChars(Tap.java:110)
   at org.netbeans.lib.terminalemulator.Term.putChars(Term.java:3257)
   at org.netbeans.modules.cnd.debugger.common2.debugger.NativeDebuggerImpl.preKill(NativeDebuggerImpl.java:1135)
Comment 1 Exceptions Reporter 2014-04-04 11:13:55 UTC
Created attachment 146545 [details]
stacktrace
Comment 2 ilia 2014-04-10 13:50:09 UTC
*** Bug 243681 has been marked as a duplicate of this bug. ***
Comment 3 ilia 2014-05-15 09:50:00 UTC

*** This bug has been marked as a duplicate of bug 244472 ***