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 168293 - Continue disabled after stepping and hitting breakpoints in debugger. Thread running state is wrong
Summary: Continue disabled after stepping and hitting breakpoints in debugger. Thread...
Status: CLOSED DUPLICATE of bug 167776
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-08 16:28 UTC by swpalmer
Modified: 2010-05-06 08:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Snapshot of 15 seconds to parse and index for Call Heirarchy (14.72 KB, application/octet-stream)
2009-09-25 17:41 UTC, swpalmer 		Details
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 swpalmer 2009-07-08 16:28:32 UTC 
When I hit breakpoints in my JavasE app and step a few times (step over, step into, step out) I find that the continue 
button becomes disabled and the thread view shows the threads as running when at least some of them aren't.  To get the 
program to move along I have to press PAUSE to force the continue button to activate then press continue again.  But when 
the code hits a breakpoint it acts as if it is still running.  So to if there is a breakpoint in a loop for example, I 
will have to pause/resume manually several times until I exit the loop because when the thread is at the breakpoint the NB 
debugger has no clue.

This happens very frequently but not every time.
Comment 1 swpalmer 2009-07-08 16:29:09 UTC 
Using JDK 6u14
Comment 2 Martin Entlicher 2009-07-08 16:51:47 UTC 
This is a duplicate of issue #167776.
Any concrete steps how to reproduce are welcomed, though I understand that this is a random bug.

*** This issue has been marked as a duplicate of 167776 ***
Comment 3 swpalmer 2009-09-25 17:41:29 UTC 
Created attachment 88377 [details]
Snapshot of 15 seconds to parse and index for Call Heirarchy
Comment 4 swpalmer 2009-09-25 17:43:57 UTC 
Excuse the accidental attachment (meant for another bug) - I hate how it steps to the next bug in the list when I add a 
comment!
Comment 5 Marian Mirilovic 2010-05-06 08:02:22 UTC 
verified duplicate