[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison GLR buffer-overflow and invalid pointer fixes
From: |
Frank Heckenbach |
Subject: |
Re: Bison GLR buffer-overflow and invalid pointer fixes |
Date: |
Fri, 8 Jul 2005 11:41:26 +0200 |
User-agent: |
semail 20050409 |
Paul Eggert wrote:
> Frank Heckenbach <address@hidden> writes:
>
> > one could of course always #define them to setjmp/longjmp, I
> > suppose.
>
> Yes, that's true, but the tricky part is how to determine whether
> they're available, without imposing on the user's name space or
> requiring Autoconf. In other areas like this, glr.c's method has
> always been to assume the latest system, so there is some precedent
> for simply using sigsetjmp.
I meant user code that doesn't want to assume the latest system
could do so, probably using autoconf itself.
Frank
--
Frank Heckenbach, address@hidden
http://fjf.gnu.de/
GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)
Message not available