lkml.org 
[lkml]   [1999]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.1: memory corruption and SIGSEGV handlers.
On Mon, 1 Mar 1999, Mark Hemment wrote:

> Hi Dick,
>
> > So you are saying that setup_frame() should reserve enough signal
> > stack-space to use the default handler if the signal stack grows
> > beyond limits? Let's look at the case of root where there is no
> > getrlimit set.
>
> No. The default action for SEGV (the signal we are interested here),
> is to drop core. This doesn't require any user-stack space (just a call
> to do_exit()).
>

But isn't that call on the signal stack?

Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.2 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
Wisdom : It's not a Y2K problem. It's a Y2Day problem.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.085 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site