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 12558 - Can debugger step into static initializer block?
Summary: Can debugger step into static initializer block?
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-01 17:49 UTC by petrula
Modified: 2010-04-29 09:08 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 petrula 2001-06-01 17:49:30 UTC 
When using step into, the debugger breaks at main.
Is it possible to have the debugger step into the first static
initializer block?

I want to avoid having to locate all the static initializer blocks and
having to set breakpoints in them. JBuilder 4 has this capability.

"Jan Jancura" <jan.jancura@czech.sun.com> said
No, it is hardcoded that current debugger stops in main not in static. But I
agree that it can be useful to create some debugger settings where to stop
on trace into. Can you add this RFE to our database
(http://debuggercore.netbeans.org/issues/enter_bug.cgi?product=debuggercore)
, please?
Comment 1 Jan Chalupa 2001-11-27 12:09:23 UTC 
Target milestone -> 3.3.1.
Comment 2 Marek Grummich 2002-07-22 09:01:16 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 3 Marek Grummich 2002-07-22 09:04:55 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 4 David-john Burrowes 2002-09-13 02:38:27 UTC 
See also: http://www.netbeans.org/issues/show_bug.cgi?id=27071
Comment 5 _ lcincura 2005-05-12 13:10:24 UTC 
This behaviour is now implemented. Debugger steps into staic initializer when
started by Step Into.
Comment 6 Quality Engineering 2010-04-29 09:08:42 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.