freenode/#sbcl - IRC Chatlog
Search
13:34:16
TeMPOraL
hi all, a question; I'm digging into SBCL's implementation of trace, trying to convert it to generate traces into a data structure (for use in situations where *trace-output* may be written to by something else, or from multiple threads)
13:35:02
TeMPOraL
i.e. I'm running trace with :report nil and :print and :print-after set to code logging data
13:36:07
TeMPOraL
now I can't figure out how to get access to the name of the function being currently traced, and after reading the source code, it seems SBCL goes out of its way to ensure I can't access it, including NULLing *current-frame* and rebinding sb-debug:arg in a way that prevents me from accessing the traced function
13:37:06
TeMPOraL
my questions: is there a good reason for preventing one from accessing the traced function like this? should I approach the problem of tracing differently?
14:02:09
pfdietz
fatal: unable to access 'https://git.code.sf.net/p/sbcl/sbcl/': The requested URL returned error: 503
17:57:59
karlosz
stassats: does that gdc transform work for (gcd a (progn (setq a 5) a) when a is 15?
18:25:40
pfdietz
That example works fine. I would expect the random tester to find any bug like that.
21:28:34
g_o
hey pretty new to hacking sbcl, is it possible to use functions from modules in "code", on "compiler" modules? when i try to access them i get an error. something about cold / warn compilation? is there a workaround or anywhere i can read an overview about that?
21:35:36
Krystof
an overview of what's going on in the build process: http://research.gold.ac.uk/2336/
21:36:54
Krystof
you are first building a compiler as an application inside a host lisp. In that application, you can use host lisp Common Lisp functions, and anything that's included in the application (basically, everything that's not marked :not-host in build-order.lisp-expr)
21:37:57
Krystof
you can't use, and shouldn't need to use, things that are marked :not-host -- typically those are things that replace host lisp functionality: for example, definitions of CL functions
21:38:03
g_o
Krystof: yeah i figured out i had a host but was looking for a flag or any way to distinguish really who is executing what
22:02:22
g_o
Krystof: oh, i actually am trying to use a :not-host, because i edited it and need some functionality there.
22:07:18
g_o
im thinking about making it the host, and then compiling with changes.. though i guess that beats the purpose of the seperation
22:11:37
pkhuong
then slammed with partial rebuilds for the last bit of iterative testing and development