Re: Internal error: lstream not open

Ben> What I'd really like to see is both a C and Lisp backtrace. If you can: Ben> [1] change signal_1() in eval.c not to be static. (this is to ensure it doesn't Ben> get compiled away into nothingness) Ben> [2] run under a debugger and put a breakpoint on signal_1. Ben> [3] turn on debug-on-error, e.g. Options->Troubleshooting->Debug On Error. Ben> when you get the error, you should be back in the debugger, and you can get a C Ben> stacktrace. Ben> you can use debug_backtrace() to get a Lisp backtrace, output on stderr or in a Ben> separate MS Windows console window. I'll try to do this as well, because I have the same problem. Note that this started happening somewhere in the b5 series or so but it was very intermittent---maybe once per month. Now with CVS sources from yesterday, it happens every few hours, whenever xemacs or my nntp server closes the connection. Also, as someone mentioned, I see this with GNUS. I don't see the error message, but xemacs starts to use 80% CPU while not doing anything. If I stop GNUS and restart it, I get the bad stream error message. Ray