Empty stack trace/method call from nowhere?

From: Michael Borgwardt (brazil_at_brazils-animeland.de)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 15:45:30 +0200

I sometimes use constructs like this:
new Exception().printStackTrace(System.out);
for debugging, in order to find out where a problematic call came from.

Now I've encountered a case where it seems the call came from nowhere:
the stack trace contains only the method with the debug output itself.
And this is consistent with what eclipse tells me about the usage of
the method: it's used in only one place where it should be followed
immediately by another debug message, but in the case I'm looking at,
that is missing.

Admittedly, this *is* an applet running in the Microsoft VM, but I find
it hard to believe that even the Microsoft VM generates calls from
nowhere.

Does this sound like a known issue? Under what circumstances can an
Exception's stack trace contain only the method in which it's created?

Relevant Pages