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 151040 - Line breakpoint corrupts state of thread
Summary: Line breakpoint corrupts state of thread
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-22 17:22 UTC by Petr Cyhelsky
Modified: 2010-04-29 09:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Cyhelsky 2008-10-22 17:22:55 UTC
Product Version: NetBeans IDE 6.5 RC1 (Build 200810220101)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b14
System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb)

Observed: line breakpoint which has condition set to true AND hit count set to multiple of 1 AND is set to stop no
threads corrupts state of its corresponding thread in debugging view - it is frequently opposite of what it should be -
"green, running" after pause, "orange, suspended" after continue. And also the debugging view flickers like crazy during
the debugging with this breakpoint set.

Steps to reproduce: set line breakpoint on line 39 of ThreadSuspending.java -> set it to stop all threads -> start
debugging - after debugger stops set the breakpoint to stop on no threads and set its condition to true and set it to
stop on hit count that is multiple of 1 -> continue -> if the the issue doesn't occur right away, try  invoking pause
and continue few times
Comment 1 Petr Cyhelsky 2008-10-24 10:34:33 UTC
reduced steps: only setting of stop no threads is crucial - it has nothing to do with either condition or hit count -
these can be safely turned off and the issue is still present.
Comment 2 Daniel Prusa 2009-05-05 13:26:43 UTC
Reproducible, but occurs only if the breakpoint is being hit repeatedly in a loop and if there is a very short interval
between two consequent hits.
Comment 3 Quality Engineering 2009-11-02 11:17:38 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX
Comment 4 Quality Engineering 2010-04-29 09:45:02 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.