Bug 1737 - Feature: filter static initializers (1GKQHTT)
Summary: Feature: filter static initializers (1GKQHTT)
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:18 EDT by Darin Wright CLA
Modified: 2001-10-31 14:54 EST (History)
0 users

See Also:

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 Darin Wright CLA 2001-10-10 22:18:28 EDT 
DW (9/27/2001 5:57:43 PM)
 from EG:

I'd like to have the option to not step into static initializers. This is 
similar to
not stepping into synthetic methods.
Comment 1 Darin Wright CLA 2001-10-12 13:57:36 EDT 
I will be done the code review for JDIThread today. You can start on this
next week.
Comment 2 Joe Szurszewski CLA 2001-10-29 18:52:44 EST 
Done.  Added Java Debug preference to control this feature.  This required 
recognizing when a step into had effectively been a no-op, because the step 
into encountered only filtered code.  In these cases, all VMs seem to put the 
instruction pointer back where the step was initiated.  This is confusing to 
the user, so there is an extra programtic step into in these case to move 
forward to the next (unfiltered) line of code.

The work to support this feature meant that we could also add a 'filter 
constructors' feature almost for free, so that has also been added.
Comment 3 Joe Szurszewski CLA 2001-10-29 18:52:57 EST 
Fixed.
Comment 4 Darin Wright CLA 2001-10-31 14:54:28 EST 
Verified.