> > Another important question to me: Are there any built-in log
> > mechanism? where and how do I write and read the logs? I started my
> > application with :debug t and still I see no difference.
/tmp/hunchentoot.log
Warnings inside the flow of the program will show up in the log.
Eg this may be useful to see what's going on with forms etc., evaluate
it at the REPL:
(defmethod update-object-view-from-request :around (obj view &rest
args
&key class-store
&allow-other-keys)
(warn (format nil "--------REQUEST PARAMETERS-------- ~%~% ~A ~%~
%" (request-parameters)))
(call-next-method))
Backtraces are probably best seen with emacs+slime: what platform are
you using? There's a tutorial on weblocks+linux, and one for OSX too
out there..
After weblocks is loaded, evaluating the following show backtraces in
slime (there's a version of slime for eclipse, afaik).
;========= Debug called from i-u-s ========
(defun init-slime-debugging ()
"Don't catch errors and redirect debugger to slime. Works great !"
(setf hunchentoot:*catch-errors-p* nil)
(setf *debugger-hook* 'swank:swank-debugger-hook))
(defmethod maybe-invoke-debugger (condition)
(unless hunchentoot:*catch-errors-p*
(let ((sb-debug:*stack-top-hint*
(or sb-debug:*stack-top-hint*
(nth-value 1 (sb-kernel:find-caller-name-and-frame)))))
(invoke-debugger condition))))
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
