From: | Richard Hansen <gentoo-a7x@×××××××××××.org> |
---|---|
To: | gentoo-hardened@l.g.o |
Subject: | [gentoo-hardened] SSP + setjmp() = badness? |
Date: | Sat, 29 Jul 2006 21:39:02 |
Message-Id: | 001101c6b357$2280c970$0201a8c0@reno |
1 | Hi all, |
2 | |
3 | I'm trying to figure out a bug in Ethereal/Wireshark that appears only when it is compiled with a gcc profile that has SSP turned on. (For details about the bug, see http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1001 and http://bugs.gentoo.org/show_bug.cgi?id=133092) |
4 | |
5 | After spending hours with gdb, I believe I have narrowed down the problem to a setjmp() call in the Wireshark code. That call seems to be trashing the stack, based on comparing local variable values before and after the call. Is this a known limitation of SSP, or should setjmp() work with SSP? |
6 | |
7 | Thanks! |
8 | |
9 | |
10 | -- |
11 | gentoo-hardened@g.o mailing list |
Subject | Author |
---|---|
Re: [gentoo-hardened] SSP + setjmp() = badness? | pageexec@××××××××.hu |
Re: [gentoo-hardened] SSP + setjmp() = badness? | "Kevin F. Quinn" <kevquinn@g.o> |
Re: [gentoo-hardened] SSP + setjmp() = badness? | Mike Frysinger <vapier@g.o> |