I wanted to know is there any specialized way to debug multithreaded applications where I want to debug for exceptions like NullPointerException which is occurring randomly for randomly chosen thread. How to deal with this kind of situations? I will be waiting for your valuable replies...
If a thread throws a fatal exception while debugging in eclipse, the offending thread should halt but the rest of the app would keep running. In the debug window, you can select the dead thread and see its stack context. I think the other threads keep running, anyway. I forget.
It's also possible to set breakpoints on NullPointerExceptions using the Eclipse breakpoint editor. The main problem here is that certain libraries are quite sloppy about using Null Pointer and Array Out Of Bounds exceptions for application purposes, which they intercept internally and keep running. So if you set a general breakpoint, you may be flooded with noise exceptions.
Customer surveys are for companies who didn't pay proper attention to begin with.
0
