Re: internal-error: lstream

Piercarlo> I get the "internal error: lstream" message every time Piercarlo> I try to decode an image in Gnus. I am using 21.4.8 Piercarlo> under SuSE 8.1, but a WWW/News search reveals this is a Piercarlo> long standing bug. sjt> Maybe it's the same one, maybe not. A backtrace from _your_ sjt> crash would help. In fact, I've spent some time trying to verify this. I've been able to reproduce the crash described by Richard Mlynarik in http://groups.google.com/groups?selm=mailman.1013561161.740.xemacs-news%4... if configured --with-mule, but not without, in 21.1.14. However, none of my standard configuration (very similar to the Red Hat configuration in Mly's report), a similar --without-mule build, and a simple --with-mule --with-x11 --without-everything-else build seems to crash in 21.4.11, and my standard build of 21.5 (current CVS) --with-mule doesn't crash. (The crash in 21.1.14 with mule invariably crashed within 15 SIGPIPEs; all of the others survived at least 100 SIGPIPEs.) Since I don't understand what the bug _was_ I won't say it's _fixed_, but behavior of recent XEmacsen is different and more stable in this respect, at least for Mly's test case. sjt> There's not much we can do if you can't provide a way for sjt> _us_ to replicate it, or at least a meaningful backtrace (ie, sjt> compiled with -g and not stripped). Since you are getting crashes and I'm not, this is really important. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.