Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Stanimir Stamenkov <s7an10@netscape.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: Avoid creating a stacktrace prior to JDK 1.7
Date: Sun, 02 Oct 2011 00:58:14 +0300
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <j682df$9ve$1@dont-email.me>
References: <j64ht6$o64$1@news.albasani.net> <j66puk$h0j$1@dont-email.me> <j66t6a$9ta$1@news.albasani.net> <4424828.699.1317485416810.JavaMail.geo-discussion-forums@prng5> <j67kk4$qf3$1@news.albasani.net> <1058576.2212.1317496868028.JavaMail.geo-discussion-forums@prfh23> <j67rp6$afo$1@news.albasani.net> <j67svg$7om$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 1 Oct 2011 21:58:07 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="7eOF4vEIiUU6n7fF+lWgFg"; logging-data="10222"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19RaTcFydc7uNmp6Dq3PLwv"
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1
In-Reply-To: <j67svg$7om$1@dont-email.me>
X-Face: "@)%Vlap6d%OVYDS}B4YUWE@yUy+^!w/+.q.,c5kjI#+uG?kYP&r/pTjNWgo:g[A,O=AL3/ j&4Le2cau$<e=FPq~GbeZ6DW1Grey[VHn8?ktzvoQtzlg;]&rh8g]CD+_BC7d[gW{Yx&_X*4Q$h&nJ l@t(|4R4:T='&]U#ui+z9OC$.~gJjU93kh:Ojc$Cz0n#I9!~!9ay?E<UlW&5,IFX1*KtA>MYEFst$y y"m]M7tq\S(>[a$x0x8%S
Cancel-Lock: sha1:Ly5k+HWp0ortCouZh/nh5WnHRGI=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8468

Sat, 01 Oct 2011 16:24:46 -0400, /Eric Sosman/:

>      Quoth the Java SE 6 Javadoc: "A throwable [sic] contains a
> snapshot of the execution stack of its thread at the time it was
> created."  That is, the Javadoc promises that a Throwable carries
> a stack trace.  A Throwable with no stack trace breaches the
> promise, and since that promise was still in force as of 1.6 I
> deduce that there's no such thing as a stackless Throwable in that
> version, or that it's a bug if there is.

You may be right, but I've read in the Javadoc for 
java.util.logging.Logger, for example 
<http://download.oracle.com/javase/6/docs/api/java/util/logging/Logger.html>:

| For the methods that do not take an explicit source name and
| method name, the Logging framework will make a "best effort" to
| determine which class and method called into the logging method.
| However, it is important to realize that this automatically
| inferred information may only be approximate (or may even be
| quite wrong!). Virtual machines are allowed to do extensive
| optimizations when JITing and may entirely remove stack frames,
| making it impossible to reliably locate the calling class and
| method.

So it seems stack trace information is not guaranteed to be 
available to user code.  This detail may be given somewhere in the 
language or VM specifications.

-- 
Stanimir