From: Deepak S. <dm...@gm...> - 2011-11-01 15:37:34
|
Hi, I tried to trace an internal SBCL package. (trace "SB-IMPL") It gives control stack overflow error. INFO: Control stack guard page unprotected CORRUPTION WARNING in SBCL pid 22057(tid 2953318400): Alternatively, I tried redefining internal SBCL package functions after unlocking package. It causes binding stack exhausted error. Next option I tried is to add trace statements to lambda-guts inside code/defboot.lisp. This is something I tried Changed from: --------------------- (lambda-guts `(,args ,@decls (block ,(fun-name-block-name name) ,@forms))) to: --- (lambda-guts `(,args ,@decls (block ,(fun-name-block-name name) ;insert trace statement here ,@forms))) where trace-statement is either a print, format or /show0 call but all result in failed builds. Really appreciate if someone can help about tracing internal sbcl packages? I have tried the SBCL build process pdf (C Rhodes) and reading through compier internals docs, but could not find the solution. Thanks in advance. -- http://deepaksurti.com To see a miracle, be the miracle. |