[hunchentoot-devel] Backtrace display

[Jonathon McKitrick]

Thanks, I'll check these out.  It looks pretty weblocks-specific, but
I assume it can be adapted to hunchentoot easily enough?  I'll just
look for a similar method  to wrap with the AROUND method.

On Tue, Sep 1, 2009 at 2:50 PM, Leslie P. Polzer<sky at viridian-project.de> wrote:
>
> Jonathon McKitrick wrote:
>> I recall some time ago, the break and backtrace capability of
>> Hunchentoot was removed, perhaps to make it less platform dependent.
>> But I still find myself often trying to find the origin of cryptic
>> error messages, and adding FORMAT and BREAK statements to narrow down
>> the problem area.  What is a good way to drop in support for, say,
>> SBCL, so that an error will break into the debugger with a backtrace,
>> or even dump the backtrace to the log file?
>
> See http://bitbucket.org/S11001001/weblocks-dev/src/tip/src/error-handler.lisp
> and http://bitbucket.org/S11001001/weblocks-dev/src/tip/src/request-handler.lisp#cl-61
>
>  Leslie
>
> --
> http://www.linkedin.com/in/polzer
>
>
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel
>



-- 

Jonathon McKitrick
http://moltencopper.com