[Sbcl-devel] Re: Output of trace in a separate thread goes somewhere else now?

[Juho S. <js...@ik...>]

<re...@ro...> wrote:
> I upgraded to SBCL 0.9.9 compiled myself on Linux Fedora Core 3 to get
> unicode support.
> 
> Now if a trace a function that is executed a different thread (such as a
> paserve worker thread)
> I can't find the output.

It's probably in the *inferior-lisp* buffer.

> Previously it would come out on my slime stream as I expected.
> 
> If I execute the same function from slime myself, I see the trace and
> "(format t" output
> as I did previously.
> 
> Have I missed some major change?  Do threads now have their own output
> streams 
> somehow?

No, but as of 0.9.6 they no longer inherit special variable bindings
(*standard-output* in this case) from the parent thread.

<http://www.sbcl.org/manual/Special-Variables.html#Special%20Variables>

-- 
Juho Snellman