Gisle S�lensminde <[EMAIL PROTECTED]> writes: > On Tue, 17 Feb 2004, Raymond Toy wrote: > >> >>>>> "Gisle" == lensminde <Gisle> writes: >> >> Gisle> The problem is that when I get some type-errors, the condition don't >> give >> Gisle> me a description of the problem or a stack trace, but just gives >> Gisle> segmentation fault.
This is merely speculation, but: is it a problem with the trap handler? I had similar symptoms on my Alpha where the instruction CMUCL was using for internal errors didn't actually cause a trap on my hardware/firmware/os version, so CMUCL would then go onto the next instruction, which was actually the error trap's data byte (and usually get a SIGILL, but this would depend on the bit patterns involved) I'm not sure how CMUCL does traps on SPARC, but if your hardware swapping has included different versions of openfirmware etc, this may be one possibility to check, -dan -- "please make sure that the person is your friend before you confirm" -- Attached file included as plaintext by Listar -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAN1tIHDK5ZnWQiRMRAg+GAJ9wrSir/mjfSujyONyjwxaQsmo9sgCgkzX9 oXyFywxH1isLiutop/zF54o= =Gchm -----END PGP SIGNATURE-----
