[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: stackovf: optionally use libsigsegv

From: Gary V. Vaughan
Subject: Re: stackovf: optionally use libsigsegv
Date: Thu, 31 Jul 2008 16:22:05 +0700

Hi Eric,

On 18 Jul 2008, at 05:17, Eric Blake wrote:

I'm committing this on the stackovf branch. This completes the original goal I had when setting out to create the branch: stack overflow detection in m4 is no longer the unsafe portability nightmare it used to be. If you install the optional library libsigsegv, this branch guarantees that on most modern porting targets, stack overflow no longer causes a core dump (cygwin, mingw) nor is an internal bug misdiagnosed as stack overflow (BSD, Linux, ...) (but we don't have any internal bugs, right?). If you are lucky enough to have a platform
that does this without libsigsegv (Solaris), more power to you.

Nice work!  More robust *and* more maintainable in one hit!?!

Next step - figure out how to make the master branch have two simultaneous gnulib checkouts (the c-stack, strsignal, and related modules are not needed
for libm4.a, just the final m4 executable).

A general solution in gnulib-tool?

If not, what is the problem with the current method we use in master?

Then I can merge this into both branch-1.6 and master.

AFAICT multiple gnulib checkouts is orthogonal to libsigsegv, and it would be nice to see this code on the dev branches right away. We can solve other problems separately :)

.  ())_.              Email me: address@hidden
.  ( '/           Read my blog: http://blog.azazil.net
.  / )=         ...and my book: http://sources.redhat.com/autobook

Attachment: PGP.sig
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]