Check for valid stack frame in longjmp.
commitb50f8e42ba3010f0141e6a482e0820f658e89b63
authorUlrich Drepper <drepper@redhat.com>
Sat, 16 May 2009 02:28:04 +0000 (15 19:28 -0700)
committerUlrich Drepper <drepper@redhat.com>
Sat, 16 May 2009 02:37:13 +0000 (15 19:37 -0700)
tree80cef469731d5857499883d45fd3424730f0db7c
parentf1342e0be8e222dbca077beca94b5937564e8c4b
Check for valid stack frame in longjmp.

If longjmp restores the stack frame to an address which is beyond
the stack frame at the time of the longjmp call it would install
an uninitialized stack frame.  If compiled with _FORTIFY_SOURCE
defined, longjmp will now bail out in this situation.
17 files changed:
ChangeLog
NEWS
Versions.def
debug/Makefile
debug/Versions
debug/longjmp_chk.c [new file with mode: 0644]
debug/tst-longjmp_chk.c [new file with mode: 0644]
include/bits/setjmp2.h [new file with mode: 0644]
include/stdio.h
setjmp/Makefile
setjmp/bits/setjmp2.h [new file with mode: 0644]
setjmp/longjmp.c
setjmp/setjmp.h
sysdeps/i386/____longjmp_chk.S [new file with mode: 0644]
sysdeps/i386/__longjmp.S
sysdeps/x86_64/____longjmp_chk.S [new file with mode: 0644]
sysdeps/x86_64/__longjmp.S