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 194878

Summary:	Flushing caches stops at debugger catchall breakpoint
Product:	platform	Reporter:	Chiana
Component:	-- Other --	Assignee:	Jaroslav Tulach <jtulach>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	P3
Version:	7.0
Hardware:	PC
OS:	Windows 3.1/NT
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Screenshot of debugger status window Screenshot

Description Chiana 2011-01-30 17:14:54 UTC

[ BUILD # : 201101300000 ]
[ JDK VERSION : 1.6.23 ]

I don't know if this is significant but I've been working on an NBM and have
noted that when you stop the IDE (after testrunning in debug-mode) it often
stops at a catch-all point flushing caches. I'm just not sure whether this is
significant or not, but in my experience anything that stops at a catch-all
point must be dealt with...
Screenshot contains what little information I can get without actually
downloading and running with the entire sourcecode...

Comment 1 Chiana 2011-01-30 17:15:50 UTC

Created attachment 105496 [details]
Screenshot of debugger status window

Comment 2 Chiana 2011-01-30 17:21:14 UTC

Created attachment 105497 [details]
Screenshot

This is some info of the exception itself and it's cause...

Comment 3 Martin Entlicher 2011-01-31 13:23:50 UTC

This was discovered by debugger, but it has nothing to do with debugger itself.
o.n.bootstrap/src/org/netbeans/Stamps.java

Comment 4 Jaroslav Tulach 2011-01-31 13:51:10 UTC

I tried to put exception breakpoint on Throwable and restrict it to Stamps class, but it does not stop.

Comment 5 Chiana 2011-02-02 01:54:45 UTC

Well, this still happens, it seems to be an IndexOutOfBounds... And it happens just before the VM terminates...

Comment 6 Jaroslav Tulach 2011-02-02 06:23:48 UTC

It does not happened to me. Can you find out the stacktrace of the IndexOutOfBoundsException when it gets created?