I am pretty confused. Is it an Android problem or a problem with Java itself? When I was debugging an Android application which works with Bluetooth, the flow stopped on an catch block of `IOException` in which I later found out that exception e was null.... It was thrown when I was trying to read from an InputStream. Yes, it was not a `NullPointerException`, but some other kind of exception which is null - better say thrown un-initialized. Is it possible? In which scenario can such unitialized exceptions be thrown? ![An exception is null... Note: it's NOT a null pointer exception!!][1] [1]: http://i.stack.imgur.com/NnGg7.png
Pls. add the code sample throwing exception.