>> I receive the SIGSEGV signal on one occasion.
>> SIGSEGV means segmentation violation.
>> I hope to know in which case the SIGSEGV signal arise.
>> Let's suppose that user program is perfect.
Harald> Next to impossible.
>> In the UNIX system aspect,
>> which Kernel Configuration Parameter can create this problem.
Harald> If we really assume the user program is perfect (which I
Harald> don't believe until I've seen it), then there is a bug in the
Or in the hardware; this is particularly common with Intel systems
using substandard hardware (e.g. without memory parity checking) or
Another, very much less probable, explanation would be a stacksize
limit which is too small.
comp.unix.programmer FAQ: see <URL: http://www.erlenstar.demon.co.uk/unix/>
or <URL: http://www.whitefang.com/unix/>