Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Stanimir Stamenkov <s7an10@netscape.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: Where am I?
Date: Thu, 13 Oct 2011 03:23:25 +0300
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <j75b1q$4dm$1@dont-email.me>
References: <tmac97tlq14j1tk7tfmule337v9sc6q1rh@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 13 Oct 2011 00:23:22 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="7eOF4vEIiUU6n7fF+lWgFg"; logging-data="4534"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18QOgf6DwQ8bS6JEe65bdTT"
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111006 Firefox/8.0 SeaMonkey/2.5
In-Reply-To: <tmac97tlq14j1tk7tfmule337v9sc6q1rh@4ax.com>
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:PARRawOEqq+OmCxU/M52N41yrbc=
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8745

Wed, 12 Oct 2011 17:04:50 -0700, /Roedy Green/:

> It would be nice for debugging to include the line number of where the
> code is when printing out the error message.  Is there a simple way to
> get it, or do you need to create a Throwable then analyse the
> stacktrace?

I guess one could also use Thread.currentThread().getStackTrace():

http://download.oracle.com/javase/6/docs/api/java/lang/Thread.html#getStackTrace%28%29

But how's the current code line useful in such a log?  If you see 
the exact message you probably already know (or could easily find) 
where in the source it is produced.  If the same message is logged 
from different locations, probably the message should be revised to 
be more specific as appropriate?

I also don't think the source line (the last stack frame) alone is 
any useful without the full stack trace to see where the call is 
originating:

http://download.oracle.com/javase/6/docs/api/java/lang/Thread.html#dumpStack%28%29

-- 
Stanimir