| Behavior doesn't match Eclipse RCP book [message #460671] |
Wed, 27 December 2006 03:59 |
Eclipse User |
|
|
|
Hi,
I'm trying to go thru the Eclipse Rich Client Platform book (Addison
Wesley) and am on Chapter 4 where they have you purposely insert a null
pointer to force a NullPointerException (when the null pointer gets
dereferenced) to show you how the debugging works. The book says my
console view should tell me which exception happened. It doesn't. Same
with the debug view. The program just terminates and says that it's
terminated. Interestingly, if I set a breakpoint on
NullPointerException, the proper point in the source code shows up. Of
course, in real life, I won't necessarily know ahead of time what kind
of exception tripped me up -- that's the point of getting the report in
the console view. Any ideas on why this is? I'm running Eclipse 3.2.1 on
Windows XP and have set up the RCP-SDK target environment (also 3.2.1)
in a separate directory as the book specifies.
Sorry to be long winded -- one other, related question. I CAN see what
exception killed me by going to the Error Log window. But, I have to
import from the .log file (that's stored in the
runtime-EclipseApplication folder to see it. Also, the delete log icon
is grayed out. The only way to reset that file is to either manually
delete it from Windows, or clear the error log and export the file on
top of that.
If it matters, I have two Eclipse workspaces that I'm using. One to play
with building Java apps, and another to build a largish RCP app. I
*don't* have the exception reporting problem with the Java app workspace
FWIW.
Thanks,
Vince
|
|
|
Powered by
FUDForum. Page generated in 0.02672 seconds
Home