debugger steps into JDK code
How do I keep the debugger from stepping into JDK classes like
PropertyChangeSupport, Component, etc.? He loads each source
file into the debugger, and I don't even know where he's getting
them (I renamed src.zip).
--
==================================================
Glenn Holmer (gholmer@ameritech.net)
--
How pleasing to the eye it is. Behold, a marvel
in the darkness!
--
-Romulan commander, Star Trek (1967)
==================================================
# 1
Glenn:
AFAIK, the JDK source must be coming from one of your mounted
filesystems, perhaps a hidden one? To check, bring up the Filesystems
tab of the Netbeans Explorer, right click the very top-level Filesystems
node and choose Customize; you'll see all the mounted filesystems in the
Customizer window. Get rid of the one (or ones) with the JDK source
code and you won't step into JDK calls anymore.
Glenn Holmer wrote:
> How do I keep the debugger from stepping into JDK classes like
> PropertyChangeSupport, Component, etc.? He loads each source
> file into the debugger, and I don't even know where he's getting
> them (I renamed src.zip).
>
> --
>==================================================
>Glenn Holmer (gholmer@ameritech.net)
>--
>How pleasing to the eye it is. Behold, a marvel
>in the darkness!
>--
>-Romulan commander, Star Trek (1967)
>==================================================
# 2
I don't think you need to remove the mounted source, setting
"Use in Debugger" to false in the properties window should be enough
Regards
Thomas
Kevin Anderson schrieb:
> Glenn:
>
> AFAIK, the JDK source must be coming from one of your mounted
> filesystems, perhaps a hidden one? To check, bring up the Filesystems
> tab of the Netbeans Explorer, right click the very top-level Filesystems
> node and choose Customize; you'll see all the mounted filesystems in the
> Customizer window. Get rid of the one (or ones) with the JDK source
> code and you won't step into JDK calls anymore.
>
> Glenn Holmer wrote:
>
>
>>How do I keep the debugger from stepping into JDK classes like
>>PropertyChangeSupport, Component, etc.? He loads each source
>>file into the debugger, and I don't even know where he's getting
>>them (I renamed src.zip).
