[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: |
Paul Hilfinger |
Subject: |
Re: Bison GLR buffer-overflow and invalid pointer fixes |
Date: |
Wed, 06 Jul 2005 17:49:26 -0700 |
> address@hidden writes:
>
> > address@hidden:~ # grep setjmp glr.c
> > #include <setjmp.h>
> > if (setjmp (yystack.yyexception_buffer) != 0)
> > address@hidden:~ # grep longjmp glr.c
> > longjmp (yystack->yyexception_buffer, 1);
> > posix doesnt specify whether setjmp will
> > save the signal context. other solution
> > possible or sigsetjmp()/siglongjmp() ?
>
> Let's wait for Paul Hilfinger to comment on this issue; or, perhaps,
> someone who has run into a real problem with it in practice.
Presumably, we should use sigsetjmp/siglongjmp and decide now whether
we want the signal context to be restored. If you contemplate using
some other mechanism, then presumably your preference is that the
signal mask NOT be reset by failure (which would be my preference).
Paul H.
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Paul Eggert, 2005/07/05
- Re: Bison GLR buffer-overflow and invalid pointer fixes,
Paul Hilfinger <=
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Paul Eggert, 2005/07/07
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Frank Heckenbach, 2005/07/07
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Paul Eggert, 2005/07/08
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Frank Heckenbach, 2005/07/08
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Paul Hilfinger, 2005/07/08
- Re: Bison GLR buffer-overflow and invalid pointer fixes, Paul Eggert, 2005/07/08
Message not available