I don't usually use dribble, being happy to cut-and-paste, but I tried it today in an attempt to send off a backtrace to someone. And I noticed that, whatever I do, I can't get debugging info / error information to be written to the dribble file.
Even something simple like: * (dribble "huh.txt") * (error "watch this") results in a nice breakloop in CMUCL, but only the error statement is written to the file, and none of the output from the break loop or further commands (until I exit out of the break). *debug-io* is a synonym stream to *terminal-io*, and *terminal-io* says that its input comes from *standard-input* and its output goes to *standard-output*. That seems like it should be alright. I'm using the CMUCL source from Jan. 26th, ILisp 5.12.0, linux. still happy to cut-and-paste, Michael -- Michael Hannemann Senior Programmer, I/NET Inc. [EMAIL PROTECTED]
