rif <[EMAIL PROTECTED]> writes:
> Is there any way to get trace to give more detailed information?
>
> For instance, right now I have a library that I've wrapped using UFFI,
> and I'm trying to learn about how to use CMUCL's alien package
> partially via tracing the alien calls in this library. So for
> instance, if I've traced alien:def-alien-routine, the trace gives me
> back something like
>
> ("DEFMACRO DEF-ALIEN-ROUTINE"
> (ALIEN:DEF-ALIEN-ROUTINE ("rfftw_create_plan" RFFTW-CREATE-PLAN)
> RFFTW-PLAN
> (N INTEGER :IN)
> (DIR FFTW-DIRECTION :IN)
> ...)
> #<unused-arg>)
>
> But I assume the ... means "more stuff that we're not telling you" ---
> is there a way to get it to expand that?
(setq debug:*debug-print-length* nil)
See <http://cvs2.cons.org/ftp-area/cmucl/doc/cmu-user/debugger.html#toc67>.
BTW, APROPOS shows there's also EXTENSIONS::*TRACE-PRINT-LENGTH* but
this variable seems to be unused.
> Or am I just misunderstanding completely. Also, can someone please
> shed light on what the "DEFMACRO DEF-ALIEN-ROUTINE" in quotes at the
> beginning
See <http://cvs2.cons.org/ftp-area/cmucl/doc/cmu-user/debugger.html#toc68>.
> and the #<unused-arg> means?
No idea.
Cheers,
Edi.
