Dear Adrian + list,
Just to confirm: xemacs 21.4.8 (locally built from CVS, without mule, on the
latest release of cygwin on a w2k box, no packages installed) just built the
tramp package cleanly: no SEGV / infinite recursion in lstreams this time.
Now I'll try it with 21.5-b6 (just for fun?).
// Conrad
----- Original Message -----
From: "Adrian Aichner" <adrian(a)xemacs.org>
To: "Conrad Scott" <Conrad.Scott(a)dsl.pipex.com>
Cc: <xemacs-beta(a)xemacs.org>
Sent: Saturday, May 11, 2002 10:51 AM
Subject: Re: SEGV in compiling tramp-util.el
>>>>> "Conrad" == Conrad Scott
<Conrad.Scott(a)dsl.pipex.com> writes:
Conrad> "Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>
Conrad> Thanks to Vin Shelton for his patch to get the ilisp
Conrad> package compiled. Now I have a SEGV in compiling
Conrad> tramp-util.el.
>>
>> This isn't really a SEGV in the usual sense (writing through a wild
>> pointer), it's an infinite loop.
Conrad> Agreed: the immediate cause of death was a SEGV but that may
well
be
Conrad> cygwin's way of mentioning that the stack has run
out.
Conrad> This is running the latest CVS HEAD copy of xemacs
>>
>> Known to have at least one such in the lstream code.
Conrad> Good: at least, it's better that a bug be known than not,
which
was the
Conrad> basis of my post really.
>> As Adrian says, for working on the packages you really should use
the
>> stable (21.1.14) or gamma (21.4.8) XEmacs. The 21.5
code is very
>> unstable right now, Mule or no Mule.
Conrad> I wasn't really trying to work on the packages: I've been
Conrad> looking (vaguely as yet) at a long standing problem in
Conrad> cygwin where XEmacs loses the output (occassionally) of
Conrad> shell commands (particularly, and most irritatingly, of
Conrad> compile output). I've got into the habit of using the CVS
Hi Conrad,
it's worth trying 21.4.8 to see whether it fixes this problem.
See
http://www.xemacs.org/Releases/21.4.8.html#summary
for the details.
Please report back!
Best regards,
Adrian
Conrad> HEAD for playing around with, and this is the first time
Conrad> for quite a while it's bitten me this badly. Anyhow I'll
Conrad> move back off the leading edge a little and keep on
Conrad> stumbling about in the code until I've got something
Conrad> useful to say.
Conrad> Thanks for the responses,
Conrad> // Conrad
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/