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.
Summary: | Display a special notification when an exception is thrown from user code. Do not use Exceptions Reporter for that. | ||
---|---|---|---|
Product: | debugger | Reporter: | Chiana |
Component: | Java | Assignee: | Martin Entlicher <mentlicher> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jskrivanek, ovrabec |
Priority: | P3 | Keywords: | UI |
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 198487 |
Bug Depends on: | 226053 | ||
Bug Blocks: | |||
Attachments: |
stacktrace
Screenshot of debugger status window |
Description
Chiana
2013-02-11 02:17:21 UTC
Created attachment 131213 [details]
stacktrace
Didn't manage to reproduce this with 7.3, however there were something fishy, could just not set my finger on it as it stepped into the unhandled exception handler now and then, I shall see if a more direct approach can shed some light on this... aka... String toString() { throw new NullPointerException("Catch this..."); } somewhere... It is a problem in se.dfx.simplesql package. It is probably some third-party library which you use. We can't help with it. Yes, I can see that too, that's the package I'm currently developing, but the question is, why is an exception thrown in my code affecting the debugger? And why is it displayed as an exception as if it had occured in the IDE? Probably you are right that debugger should catch the exception. Passing to debugger category for evaluation. I agree that we should display the error in user code in another way. My suggestion would be that a "better" dialog is displayed if an exception is thrown from the .toString() informing that it was thrown from user code and suggest an alternate method of displaying the value as there exists one method (telling the debugger what method to be used for the particular class) to do this. An alternate method is to use some sort of flagging for a "debugger safe" method to use instead, something like; @Deprecated private String debugSafeToString() { return "safe"; } or like; private String toString(Object notUsed) { return "safe"; } the latter can easily be autodetected and used by the debugger if present. *** Bug 226224 has been marked as a duplicate of this bug. *** Created attachment 131486 [details]
Screenshot of debugger status window
This is what is in the variables windows showing the red-marked entry blown up.
*** Bug 226226 has been marked as a duplicate of this bug. *** *** Bug 226227 has been marked as a duplicate of this bug. *** *** Bug 226228 has been marked as a duplicate of this bug. *** *** Bug 226229 has been marked as a duplicate of this bug. *** *** Bug 226231 has been marked as a duplicate of this bug. *** *** Bug 226233 has been marked as a duplicate of this bug. *** *** Bug 226234 has been marked as a duplicate of this bug. *** *** Bug 226235 has been marked as a duplicate of this bug. *** omg, martine, i've been looking at this for about two hours and eventually realized this has already been fixed: in bug 227618. *** This bug has been marked as a duplicate of bug 227618 *** |