At 10:02 pm, Tuesday, October 21 2003, Ken Foskey mumbled:
> The following code behaves the same under K 2.4 and K 2.6 so there is
> something different for SEGV to SIGINT. Can anyone explain?
>
Of course. POSIX Says that behaviour after catching a SIGSEGV is undefined.
Anything could happen. If you catch a SIGSEGV and your machine catches fire
and jumps out the window, POSIX allows for it.
Cheers,
--
Steve
<dark> Unix's elegant and suave design makes it seem slightly older than it
really is.
* StevenK waits for Unix to have a mid life crisis and start dating operating
systems half it's age.
<Mithrandir> StevenK: it's called samba.
<dark> Mithrandir: Such lack of taste.
<dark> If you're going to date operating systems half your age, then at least
make sure they're bouncy and cute.
<dark> Maybe it's just a sexual thing. Windows goes down easily, and Unix
can stay up forever.
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
