You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Costin Manolache <cm...@yahoo.com> on 2002/10/09 23:36:02 UTC

Deep stack traces ?

Any news on the deep stack trace issue ?

( i.e. displaying not only the stack trace, but also the real cause 
when it can be determined, like JDK1.4 logging does )

-- 
Costin



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Deep stack traces ?

Posted by Niclas Hedhman <ni...@ewarna.com>.
On Thursday 10 October 2002 05:58, Ceki Gülcü wrote:
> At 14:36 09.10.2002 -0700, you wrote:
> >Any news on the deep stack trace issue ?
> >
> >( i.e. displaying not only the stack trace, but also the real cause
> >when it can be determined, like JDK1.4 logging does )
>
> The last time I checked (jdk1.4.0_01), JDK 1.4 does not do deep stack
> traces. Are you sure?

Isn't he talking about recursively picking up the Throwables in 
Throwable.getCause()??

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Deep stack traces ?

Posted by Ceki Gülcü <ce...@qos.ch>.
At 14:36 09.10.2002 -0700, you wrote:
>Any news on the deep stack trace issue ?
>
>( i.e. displaying not only the stack trace, but also the real cause
>when it can be determined, like JDK1.4 logging does )

The last time I checked (jdk1.4.0_01), JDK 1.4 does not do deep stack 
traces. Are you sure?

>--
>Costin

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>