This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 'stack overflow' message for Darwin; host hooks


On 10-Feb-2003, Geoffrey Keating <geoffk@apple.com> wrote:
> On Friday, February 7, 2003, at 11:03  PM, Fergus Henderson wrote:
> >Changing which signal is sent would be nice in the long term, but that
> >could indeed cause backwards compatibility problems, so I'm not 
> >suggesting
> >that.  Instead, I'm suggesting just changing the default behaviour when
> >a SIGBUS signal is received and the current signal handler for SIGBUS
> >is SIG_DFL.  The default behaviour should IMHO be to print a reasonable
> >error message to stderr before terminating the process.
> 
> This is such a bad idea it's hard to start explaining why it will never 
> happen.  Consider, for instance, what would happen if the user program 
> is really a database server that has closed stdin/stdout/stderr and 
> happens to have fd 2 open on its database backing store.

OK, I'm convinced.  Since there does not seem to be any reasonable way
to implement this in libc or the kernel without introducing a new
signal, which could raise backwards compatibility concerns, I guess
patching GCC is the only alternative for now.  So I withdraw my objections.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]