I used this method:
(defun print-error-log (eout e)
(format eout "Unhandled error detected: ~%")
(format eout "~A~%" e)
(when (c-code::error-data-p)
(format eout "Additional error data: ~%~A~%" (c-code::get-error-data)))
(format eout "Backtrace: ~%")
(loop for x from (- (si::ihs-top)
03.02.2013, 05:34, "Peter Enerccio" :
> I actually got it working, so it was most likely problem on my side. Thanks!
Could you share your findings? What is the right reciepe for printing backtrace?
--
The Go Parallel Webs
On Sun, 3 Feb 2013 02:32:42 +0100
Peter Enerccio wrote:
> I actually got it working, so it was most likely problem on my side. Thanks!
You're welcome, and I'm glad that it works,
--
Matt
--
Everyone hates slow websites
I actually got it working, so it was most likely problem on my side. Thanks!
2013/1/31 Matthew Mondor
> On Thu, 31 Jan 2013 17:03:44 -0500
> Matthew Mondor wrote:
>
> > Hmm that's not impossible, especially if it's a recent migration or
> > concerns mostly the bytecode interpreter (which I hav
On Thu, 31 Jan 2013 17:03:44 -0500
Matthew Mondor wrote:
> Hmm that's not impossible, especially if it's a recent migration or
> concerns mostly the bytecode interpreter (which I have less experience
> with except for the REPL).
s/migration/regression/ of course :)
--
Matt
On Thu, 31 Jan 2013 22:48:24 +0100
Juan Jose Garcia-Ripoll wrote:
> On Wed, Jan 30, 2013 at 5:06 PM, Peter Enerccio wrote:
>
> > Well, I am trying to get with handler-bind, however, it still prints
> > nothing at all (for the backtrace, I mean)
> >
>
> Probably what Anton said is the origin of
On Wed, Jan 30, 2013 at 5:06 PM, Peter Enerccio wrote:
> Well, I am trying to get with handler-bind, however, it still prints
> nothing at all (for the backtrace, I mean)
>
Probably what Anton said is the origin of your problems. I need some time
to look into this. Could you please file a bug re
By the way, anton, your guess is right.
> ((lambda () (si::ihs-fun 1)))
#
directly from ecl repl..
2013/1/31 Peter Enerccio
> I managed to grab c stack (on linux anyways) which is nice, but not that
> very revealing for any bytecoded functions...
>
> Unhandled error detected:
> something wen
I managed to grab c stack (on linux anyways) which is nice, but not that
very revealing for any bytecoded functions...
Unhandled error detected:
something went hairy
Backtrace:
C stack:
/media/home/home/enerccio/
projects/gaia/gaia/Debug/gaia(c_stack+0x62) [0x4024ae]
/media/home/home/enerccio/pro
Another guess (sorry if I am mistaken).
Do you run this code from the main REPL thread or from another thread?
I remember I debugged hunchentoot on ECL and wanted stack trace
of error happened during request handling (hunchentoot runs
request handlers in separate threads).
As you did, I looked a
On Thu, 31 Jan 2013 07:58:17 +0100
Peter Enerccio wrote:
> Even if I put declaim in the file, it is still compiled with
> DEBUG 0
>
> ;;; Compiling /media/home/home/enerccio/
> projects/gaia/gaia/src/postinit.lisp.
> ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
If I remember th
Even if I put declaim in the file, it is still compiled with
DEBUG 0
;;; Compiling /media/home/home/enerccio/
projects/gaia/gaia/src/postinit.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
2013/1/31 Matthew Mondor
> On Wed, 30 Jan 2013 17:06:47 +0100
> Peter Enerccio wrot
On Wed, 30 Jan 2013 17:06:47 +0100
Peter Enerccio wrote:
> Well, I am trying to get with handler-bind, however, it still prints
> nothing at all (for the backtrace, I mean)
Was the code compiled with an optimize debug level 2 or over? I think
that to get backtraces I needed that.
i.e. at the s
Well, I am trying to get with handler-bind, however, it still prints
nothing at all (for the backtrace, I mean)
(defun handle-any-error-log (e)
(print "x") ; checking that we are indeed in the handler
(with-open-file (eout "errors.txt"
:direction :output)
(format eout "Unhandle
In CL you usually can't get stack trace "out of condition".
Usually you can get the current stack trace. I.e. before stack is unwound.
I.e. catching error handler-bind you can get stack trace, because you are still
inside the stack, but for example with handler-case you are invoked after
the stack
I tried looking it up there, however it uses si::ihs-top/si::ihs-fun, which
at the condition handlers are for some reason 0 so there is nothing to do
at that point.
2013/1/30 Stas Boukarev
> Peter Enerccio writes:
>
> > Hello, I was wondering if it is possible to get the stack of thrown
> > co
Peter Enerccio writes:
> Hello, I was wondering if it is possible to get the stack of thrown
> condition.
> I dont think there is ansi way of doing that, however, I can see stack
> generated by conditions thrown in slime with ecl, so there must be a way to
> do it.
You can look at swank-ecl.lisp
Hello, I was wondering if it is possible to get the stack of thrown
condition.
I dont think there is ansi way of doing that, however, I can see stack
generated by conditions thrown in slime with ecl, so there must be a way to
do it.
Thanks for any pointers on how to do it.
--
Bc. Peter Vaňušanik
18 matches
Mail list logo
