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 6737 - java.lang.ArrayIndexOfBoundsException while starting debugging
Summary: java.lang.ArrayIndexOfBoundsException while starting debugging
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: All All
: P4 normal (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-05-22 23:23 UTC by Antonin Nebuzelsky
Modified: 2002-07-19 15:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2000-05-22 23:23:48 UTC 
When I pressed F5 to start the debugger the following exception was written on console, the debugger did not start and the debugging in menu and toolbars was disabled:

java.lang.ArrayIndexOfBoundsException
at org.openide.actions.DebuggerPerformer$StartDebugThread.run (DebuggerPerformer.java:306)

When I restarted Forte and tried again, the debugger started OK.
This bug appeared on Win2000 with jdk1.3, JPDA debugger without classic flag.
I was not able to reproduce it then.
Comment 1 Marek Grummich 2000-07-25 09:29:59 UTC 
Priority is changed to P4 (normal).
Comment 2 Jan Stola 2000-08-02 11:23:59 UTC 
Verified in Build 1069 and 2011.
Comment 3 Antonin Nebuzelsky 2001-04-24 12:58:08 UTC 
This problem still appears in FFJ2.0, build 1160 with JP1. The problem persists
probably also in the main trunk.

A customer complained about this exception:

Tue Apr 24 10:57:23 CEST 2001java.lang.ArrayIndexOutOfBoundsException: null
java.lang.ArrayIndexOutOfBoundsException
at
org.openide.actions.DebuggerPerformer$StartDebugThread.run(DebuggerPerformer.java:306)
Comment 4 Daniel Prusa 2001-05-23 11:02:57 UTC 
The problem have probably persisted in case when the debugger was started by 
Trace Into action. It is fixed now (in main trunk). I reviewed the code 
performed after Start Debugger action (F5) and it should be OK (there is only 
one array used and its size is checked before its element is accessed).