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 135204 - java.lang.ArrayIndexOutOfBoundsException when moving breakpoints between groups
Summary: java.lang.ArrayIndexOutOfBoundsException when moving breakpoints between groups
Status: RESOLVED DUPLICATE of bug 139692
Alias: None
Product: platform
Classification: Unclassified
Component: Explorer (show other bugs)
Version: 6.x
Hardware: All Linux
: P4 blocker (vote)
Assignee: t_h
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2008-05-16 10:09 UTC by Petr Cyhelsky
Modified: 2009-04-29 12:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (1.84 KB, text/plain)
2008-05-16 11:44 UTC, Petr Cyhelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Cyhelsky 2008-05-16 10:09:54 UTC
Product Version: NetBeans IDE Dev (Build 200805150003)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11
System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb)

Observed: When moving line breakpoint from one group to another the exception poped. After closing the exception the
breakpoints could be moved normally. when trying to reproduce it - sometimes the exception didn't occur, but the
breakpoint could not be moved, sometimes everything worked fine

Expected: The breakpoint should just be moved to another group

Steps to reproduce:toggle few line breakpoints in some java source -> in the breakpoints view select at least two and
set a group name for them by invoking "Set Group Name" from popup menu. -> set a different group name for another
breakpoint -> set the group name of one of the former group to the name of the latter group
Comment 1 Daniel Prusa 2008-05-16 11:06:19 UTC
I have tried to reproduce it but I have not been successful. Could you attach the exception's stack trace, please?
Comment 2 Petr Cyhelsky 2008-05-16 11:44:50 UTC
Created attachment 61477 [details]
stack trace
Comment 3 Daniel Prusa 2008-05-21 15:18:42 UTC
It is still hard to reproduce for me, seems to occur rarely, any additional hints how to obtain the exception with a
good probability are welcomed.

The problem is somewhere in nodes visualization, not necessary bug in debugger. It does not break debugger functionality
and it is not visible so much => decreasing priority to P4.
Comment 4 Petr Cyhelsky 2008-05-21 16:56:53 UTC
It was hard to reproduce for me too - seems to occur more often if u manipulate with the breakpoint groups a lot, but
still not every time.
Comment 5 Martin Entlicher 2008-11-18 20:45:41 UTC
Nothing from debugger on the stack trace.
Comment 6 t_h 2009-04-29 12:27:32 UTC

*** This issue has been marked as a duplicate of 139692 ***