|
|
|
|
Re: Not getting nullpointer's stack trace on console (java code) [message #988297 is a reply to message #988254] |
Thu, 29 November 2012 10:13 |
Antti Rumpunen Messages: 5 Registered: November 2012 |
Junior Member |
|
|
I tested with a simple code (Integer i = null; if(i>0)) which will cause a nullpointer every time I press a button. The code is executed twice by the same thread every time I press the button. Sometimes I get two nullpointer stack traces on the console (without Eclipse stopping the AWT-EventQueue-0 thread) and sometimes I get only one stack trace on the console and Eclipse stopping the AWT-EventQueue-0 thread.
Here is what Eclipse shows me...
Thread...
Thread...
Thread [AWT-EventQueue-0] (Suspended (exception NullPointerException))
EventDispatchThread.run() line:156 [local variables unavailable]
Thread...
Thread...
I can't provide the real code because there is thousands of lines of code and I have no idea where the nullpointer comes from. I debugged what the thread (AWT-EventQueue-0) is doing after I press the button (not my test button). The whole execution goes well. But once the thread starts to do something else (no idea what) I get the nullpointer (with Eclipse stopping the thread every time)...
[Updated on: Thu, 29 November 2012 10:14] Report message to a moderator
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08843 seconds