From: Mikael Pettersson <mikpe@it.uu.se>
To: "Warlich, Christof" <christof.warlich@siemens.com>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
Mikael Pettersson <mikpe@it.uu.se>,
Andi Kleen <andi@firstfloor.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: X86 fpu registers in a signal handler's ucontext
Date: Thu, 2 May 2013 13:12:25 +0200 [thread overview]
Message-ID: <20866.18969.21166.669069@pilspetsen.it.uu.se> (raw)
In-Reply-To: <6D83E89737156549AEA25EF9ED712C5DE481@DEFTHW99EK1MSX.ww902.siemens.net>
Warlich, Christof writes:
> richard -rw- weinberger <richard.weinberger@gmail.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.
next prev parent reply other threads:[~2013-05-02 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 14:34 Warlich, Christof
2013-04-29 17:57 ` Andi Kleen
2013-04-30 6:35 ` Warlich, Christof
2013-04-30 11:28 ` Mikael Pettersson
2013-04-30 13:45 ` Warlich, Christof
2013-04-30 14:42 ` Mikael Pettersson
2013-05-02 5:42 ` Warlich, Christof
2013-05-02 7:06 ` richard -rw- weinberger
2013-05-02 7:43 ` Warlich, Christof
2013-05-02 9:04 ` Warlich, Christof
2013-05-02 11:12 ` Mikael Pettersson [this message]
2013-05-03 3:18 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20866.18969.21166.669069@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=andi@firstfloor.org \
--cc=christof.warlich@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®