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.
If you add src.jar or other jars to a java platform they have debugging turned off by default (in Window --> Debugging --> Sources). I thing that the default should be to have it turned on.
I don't think this is a defect. We already had that on by deafult but many users were really confused when debugging their apps and suddenly debugging some unknown source (JDK), it was very difficult to keep debugger just in user application code. Stepping into JDK sources is sort of hardcore debugging and user who needs to do that can enable it by himself easily. It could be probably solved in Platform Manager by checkbox "Use Sources for Debugging".
I was really confused when I tried step into (F7) and it ended in hell. If they don't want to step inside they can use F8, cannot they?
Of course they can ... if users do *only* what is right and required we wouldn't need 70% of all code - I mean the code that does error handling. I still think that it's more acceptable for experienced user to turn in ON than for unexperienced to step into some "strange" code without knowing how to get out or how to turn in OFF. In pre-ant-projects era it wasn't ON by default either.
I assume I am experienced user. But if I would not be reading nbusers I would *never* find out. What saved me was that I remember that Tom Ball gave some advice some time ago: http://www.netbeans.org/servlets/ReadMsg?listName=nbusers&msgNo=53658 If this was not there I would not be able to debug at all and I would have to use something else than NetBeans. Do you think this is what we really want? BTW what is wrong in stepping through JDK code? Can you show me how many users were confused?
I understand David's confusion, we need to reconsider the current design. See also issue #52601.
Already implemented.