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 172109 - Debug stepping
Summary: Debug stepping
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-13 16:37 UTC by vonnie
Modified: 2010-05-06 11:51 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 vonnie 2009-09-13 16:37:12 UTC 
As I step through in debug, the netbeans locks up after a few steps.  I have to use Windows Task Manager to kill 
NetBeans.  It seems the number of steps before the lock seems fewer steps.  The Task Manager kill may leave items that 
makes the number of acceptable steps lessen.  Memory seemed the problem when this problem had first occurred.  Now, 
the memory does not seem overly extended when this happens.  

It is okay for multiple debug starts, but once into the debug walk, only a few steps are allowed.  It is especially a 
problem in a loop, but not always.

Thanks, Vonnie
Comment 1 Martin Entlicher 2009-09-14 12:44:45 UTC 
Well, in the case when netbeans locks up, we need to have a full thread dump. Please have a look at
http://wiki.netbeans.org/GenerateThreadDump and attach the thread dump here.
Thanks.
Comment 2 Vojtech Sigler 2009-09-18 11:52:04 UTC 
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested
information and reopen issue. Thanks in advance.

This could be a duplicate of issue #168613. If so, it is already fixed and patch is on updatecenter.
Comment 3 Marian Mirilovic 2010-05-06 11:51:37 UTC 
closing incomplete issues