Yes, thanks!
On Friday, October 18, 2013 12:42:00 PM UTC-7, Stanislav Sedov wrote:
>
>
> On Oct 18, 2013, at 12:35 PM, Brian Craft >
> wrote:
>
> > ah, sorry, that's a shell tool? I meant dumping a stack trace from code.
> Throwing & catching works, it's just a bit goofy. Like
> >
> > (defn-
On Oct 18, 2013, at 12:35 PM, Brian Craft wrote:
> ah, sorry, that's a shell tool? I meant dumping a stack trace from code.
> Throwing & catching works, it's just a bit goofy. Like
>
> (defn- stack-trace [msg]
> (try
> (throw (IllegalArgumentException. msg))
> (catch IllegalArgumentE
ah, sorry, that's a shell tool? I meant dumping a stack trace from code.
Throwing & catching works, it's just a bit goofy. Like
(defn- stack-trace [msg]
(try
(throw (IllegalArgumentException. msg))
(catch IllegalArgumentException e
(stacktrace/print-stack-trace e
On Friday,
> jstack
On Fri, Oct 18, 2013 at 9:44 AM, Brian Craft wrote:
> In trying to understand how threads work I'd like to dump a stack trace at
> various places. All the stack trace calls take an exception. Is there some
> simpler way, or should I throw & catch an except just to get a stack trace?
>
In trying to understand how threads work I'd like to dump a stack trace at
various places. All the stack trace calls take an exception. Is there some
simpler way, or should I throw & catch an except just to get a stack trace?
--
--
You received this message because you are subscribed to the Go
