lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 2 May 2013 13:12:25 +0200 From: Mikael Pettersson <mikpe@...uu.se> To: "Warlich, Christof" <christof.warlich@...mens.com> Cc: richard -rw- weinberger <richard.weinberger@...il.com>, Mikael Pettersson <mikpe@...uu.se>, Andi Kleen <andi@...stfloor.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RE: X86 fpu registers in a signal handler's ucontext Warlich, Christof writes: > richard -rw- weinberger <richard.weinberger@...il.com> writes: > > Are you telling us that Ubuntu shipped the wrong header file? > > Hmm - at least I still don't know how to get the right definition > of uc_mcontext (with eglibc-2.13 on Ubuntu 11.10) ... > > If I include both signal.h and asm-generic/ucontext.h, gcc reports > this error: > > /usr/include/asm-generic/ucontext.h:4:8: error: redefinition of 'struct ucontext' > /usr/include/i386-linux-gnu/sys/ucontext.h:119:16: error: previous definition of 'struct ucontext' > > Thus, signal.h obviously includes the wrong i386-linux-gnu/sys/ucontext.h > defining uc_mcontext to be of type mcontext_t. > > So is it still me doing something wrong or or _did_ Ubuntu ship > the wrong header files? #include <signal.h> #include <ucontext.h> has worked for my SIGFPE handlers on Linux for the last 10+ years on various distros and target architectures. Can we stop this thread now? There is no _kernel_ issue here. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists