> * In message <3A3C7D7D.ECF80B47@...>
> * On the subject of "Re: [clisp-list] Q: what causes sigsegv"
> * Sent on Sun, 17 Dec 2000 16:46:53 +0800
> * Honorable bruce <bruce253@...> writes:
>
> I'm using clisp-2000-03-06 on Linux/i686.
>
> In order to produce such a bug report, I need detailed help.
you need to tell us how to reproduce your crash.
I.e., you will have to send us the transcript of the entire session.
E.g., like this:
$ clisp -q
> (load "crash.lisp")
segmentation fault
$
and then send us the file "crash.lisp".
please try to make the file as small as possible.
--
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel&gt;
Read what the Arab leaders say to their people on <http://www.memri.org/&gt;
MS DOS: Keyboard not found. Press F1 to continue.

Sam Steingold wrote:
> > * In message <3A3C20E6.3842D74F@...>
> > * On the subject of "[clisp-list] Q: what causes sigsegv"
> > * Sent on Sun, 17 Dec 2000 10:11:50 +0800
> > * Honorable bruce <bruce253@...> writes:
> >
> > What does the following sigsegv mean?
> >
> > *** - handle_fault error2 ! address = 0x6C0078 not in
> > [0x20234000,0x2098DDC4) !
> > SIGSEGV cannot be cured. Fault address = 0x6C0078.
> >
> > After the signal the CLISP process died.
> >
> > Does it mean that there is some bug in my programs, such as array index
> > out of range?
>
> no, this is a bug in CLISP.
> which version are you using?
> on what OS?
> architecture?
>
> Please try to create a self-contained bug report and send it to this
> list.
>
> Thanks.
I'm using clisp-2000-03-06 on Linux/i686.
In order to produce such a bug report, I need detailed help.
I found one previous message from Bruno in that direction, but that requires
recompile clisp using different compile parameter, which seems not for this case.
Best!
Shouxun

> * In message <3A3C20E6.3842D74F@...>
> * On the subject of "[clisp-list] Q: what causes sigsegv"
> * Sent on Sun, 17 Dec 2000 10:11:50 +0800
> * Honorable bruce <bruce253@...> writes:
>
> What does the following sigsegv mean?
>
> *** - handle_fault error2 ! address = 0x6C0078 not in
> [0x20234000,0x2098DDC4) !
> SIGSEGV cannot be cured. Fault address = 0x6C0078.
>
> After the signal the CLISP process died.
>
> Does it mean that there is some bug in my programs, such as array index
> out of range?
no, this is a bug in CLISP.
which version are you using?
on what OS?
architecture?
Please try to create a self-contained bug report and send it to this
list.
Thanks.
--
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel&gt;
Read what the Arab leaders say to their people on <http://www.memri.org/&gt;
Don't take life too seriously, you'll never get out of it alive!

Dear list members,
What does the following sigsegv mean?
*** - handle_fault error2 ! address = 0x6C0078 not in
[0x20234000,0x2098DDC4) !
SIGSEGV cannot be cured. Fault address = 0x6C0078.
After the signal the CLISP process died.
Does it mean that there is some bug in my programs, such as array index
out of range?
Best!
Shouxun
--
The perversity of nature is nowhere better demonstrated by the fact that, when
exposed to the same atmosphere, bread becomes hard while crackers become soft.