Re: sigsev in eval.c

To: mdj@nada.kth.se
Subject: Re: sigsev in eval.c
From: Klaus.Schilling@home.ivm.de
Date: Sat, 19 Dec 1998 18:30:24 +0100
CC: jostobfe@calvados.zrz.TU-Berlin.DE, guile@cygnus.com, mdj@nada.kth.se
In-reply-to: <xy767b81hsj.fsf@mdj.nada.kth.se> (message from Mikael Djurfeldton 19 Dec 1998 12:40:28 +0100)
Message-Id: <E0zrQCu-00006J-00@debian>
References: <199812182006.UAA16757@linux.zrz.TU-Berlin.DE> <xy767b81hsj.fsf@mdj.nada.kth.se>
Reply-to: Klaus.Schilling@home.ivm.de
Sender: owner-guile@cygnus.com

   X-From_: owner-guile@cygnus.com  Sat Dec 19 14:17:18 1998
   Cc: guile@cygnus.com
   Cc: mdj@nada.kth.se
   From: Mikael Djurfeldt <mdj@nada.kth.se>
   Date: 19 Dec 1998 12:40:28 +0100
   Sender: owner-guile@cygnus.com
   Precedence: bulk

   Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:

   > The following code is nonsense but a segfalut should never
   > happen:

   No.

And what about SIGIOTs? Should they happen?
--
Klaus Schilling

Follow-Ups:
- Re: sigsev in eval.c
  - From: Mikael Djurfeldt <mdj@nada.kth.se>

References:
- sigsev in eval.c
  - From: Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE>
- Re: sigsev in eval.c
  - From: Mikael Djurfeldt <mdj@nada.kth.se>

Prev by Date: Re: set! prototype implementation
Next by Date: Re: set! prototype implementation
Prev by thread: Re: sigsev in eval.c
Next by thread: Re: sigsev in eval.c
Index(es):
- Date
- Thread

Guile Home | Main Index | Thread Index