You may want to look at Bug ID:4292742 at URL:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4292742
since Bug ID:4966410 was declared:
"Closed, duplicate of 4292742"
The report on Bug ID:4292742 states that this bug is:
"Fixed by reworking the "built-in" exception processing. Now all cold
exceptions (first few times) are handled by uncommon traps."
for 1.5.0. What JVM version are you using? If not 1.5.0 can you
upgrade?
As for the switches, the JVMDI is described here:
http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jvmdi-spec.html
and in the comments on Bug ID:4292742 they state that:
"In recent updates of the 1.4.2 VM (_05), use the flag
-XX:+FullSpeedJVMDI, even without jvmdi turned on. This may make
compilation performance suffer, so it is not the default."
So I'm guessing that setting that switch to true enables JVMDI in the
compiler which allow a stacktrace to be generated during "full-speed"
debugging?
And also in Bug ID:4292742 it states:
"After recompilation, the compiler may choose the older, faster tactic,
under control of the switch -XX:+OmitStackTraceInFastThrow (default
true)."
So I'm guessing that setting it false would likely mean that it won't
omit the stack trace? :-)
Good luck!
--- lei.han@xxxxxxxxxxxxx wrote:
> I found a java bug report
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4966410
> very similair like what I am experiencing.
>
> It even has an example there which you can run to test.
>
> But I don't quite get the solution given there. Does anyone know what
>
> "-XX:+FullSpeedJVMDI" and "-XX:-OmitStackTraceInFastThrow" does? How
> would
> those options fix this problem?
> Thanks!
>
> Lei Han || Home : (248) 6149056 Cell: (513)6074271
> ----- Forwarded by Lei Han/CIMG/CVG on 08/22/2006 02:38 PM -----
>
> Lei Han/CIMG/CVG
> 08/18/2006 10:53 AM
>
> To
> users@xxxxxxxxxx
> cc
>
> Subject
> printStackTrace prints nothing
>
>
>
>
>
> My code has logic like
>
> java.io.StringWriter writer = new java.io.StringWriter();
> e.printStackTrace(new java.io.PrintWriter(writer));
> String stackTraceString = writer.toString();
>
> buf.append(stackTraceString);
>
> LOG.error(buf);
>
> But in my log file I only see
>
> java.lang.NullPointerException
>
> There is no stack trace after it and also no print out like <<no
> stack
> trace available>>
>
> How come the stack trace of java.lang.NullPointerException has not
> been
> printed out?
>
> Thanks!
>
> Lei Han || Home : (248) 6149056 Cell: (513)6074271
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|