Re: SIGSEGV cannot be cured

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...3-vap.pbz> [2005-10-01 16:18:32 -0700]:
>
> I've been getting the above segfault message recently (since moving to
> Fedora Core 4).  The first time I got it from an old reliable 2.31
> running an old reliable application (mail server) and I thought
> perhaps it was related to libsigsegv (which I reinstalled - didn't
> help), and eventually just to get the server running again moved it to
> 2.35, which didn't give me the segfault.  I noticed while I was
> looking that, although the crash occurred the first time the server
> was contacted, I also got the same error from something as simple as
> clisp (compile-file "...")  Later I switched to a different xemacs
> version and found that now I got the same errors from 2.35.  I went
> back to 2.31 and that worked.  Now I switch back and get the errors
> again from 2.31 but not 2.35.  I also notice that I don't get the
> error from a new xterm.  I'm trying to understand what the problem is
> and how it is caused by the xemacs from which I run.  The two have
> slightly different environments, but I've tried unsetting most of the
> variables with no effect in either case................

can you produce a small reliable test case that triggers the bug?
if yes, please do.
if not, please try to debug.
see
http://clisp.cons.org/impnotes/faq.html#faq-debug
http://clisp.cons.org/impnotes/gc-safety.html


-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.honestreporting.com> <http://www.dhimmi.com/>
<http://www.iris.org.il> <http://www.camera.org> <http://www.savegushkatif.org>
Experience comes with debts.