Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes:
Hrvoje Niksic <hniksic(a)iskon.hr> writes:
> Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes:
>
> > After Martin's fix for the Fmapconcat crashes I wanted to reenable the
> > test in base64-tests.el which Hrvoje had disabled some time ago,
>
> I haven't it.
I was referring to the following:
(when nil
;; This code crashes XEmacs! This requires further investigation.
;; I'm running Linux, and for me, XEmacs crashes in
;; Fmapconcat()->mapcar1(), after a GC that thrashes the stack.
;; Raymond Toy reports a similar crash under Solaris.
(loop for (raw encoded) in bt-test-strings do
...
The code does not look that way in my version. As with most memory
corruption problems, the crashes came and went as *they* saw fit.
My version goes like this:
(when t
;; This code crashes some versions of XEmacs 21.2! This requires
;; further investigation. I (hniksic) am running Linux, and for me,
;; XEmacs used to crash in Fmapconcat()->mapcar1(), after a GC that
;; thrashes the stack. Raymond Toy reported a similar crash under
;; Solaris. I can no longer repeat the bug, so I cannot fix it now.
(loop for (raw encoded) in bt-test-strings do
...
> The base64-tests file has been broken in the repository for a
long
> time, and I'm still waiting for someone to fix it. The problem was
> that that file used to have a raw-zero character embedded in it,
> which CVS apparently doesn't grok. Even worse, I can't find a way
> to fix the situation, even after having removed the offending
> character.
Wouldn't directly hacking the RCS file help?
It would, but I don't think I'm supposed to do that. Given that I
know next to nothing about RCS, I definitely don't think I'm the right
person for the job.
Otherwise why don't we just remove the existing file and add a
fresh
copy?
I tried that. It didn't work.
> If you want, I'll mail you a working copy of the file.
thanks. I have one, back from the time when you first added it.
But the file got updated several times. Here is my latest version: