From: "Ted Ts'o" <tytso@mit.edu>
To: Kees Cook <keescook@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Correct way to include siginfo.h?
Date: Tue, 27 Mar 2012 10:21:33 -0700 [thread overview]
Message-ID: <20120327172133.GB10142@thunk.org> (raw)
In-Reply-To: <CAGXu5jK3ezCN2=hy=AARh=T9L8YzCTKAXH6dbAH7FGX3P8VkoQ@mail.gmail.com>
On Tue, Mar 27, 2012 at 10:01:10AM -0700, Kees Cook wrote:
>
> Does anyone know the right way to include siginfo.h when building
> userspace tools that need it?
What fields or structures are you trying to get at? I haven't needed
to include siginfo.h explicitly even though this file pokes and prods
pretty thoroughly at the siginfo structures:
http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=blob;f=e2fsck/sigcatcher.c;h=10b93287d5b2b4da1fb43d34fafd848d06c01645;hb=5f7c04972fefa8198c34f231a9e8a5430705b4ab
The sigcatcher.c file is a debugging tool for e2fsprogs that prints
pretty much everything that is available to userspace, as far as I
know...
- Ted
next prev parent reply other threads:[~2012-03-27 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 17:01 Correct way to include siginfo.h? Kees Cook
2012-03-27 17:21 ` Ted Ts'o [this message]
2012-03-27 17:29 ` Kees Cook
2012-03-27 17:37 ` Ted Ts'o
2012-03-27 18:01 ` Kees Cook
2012-03-29 17:58 ` H. Peter Anvin
2012-03-29 18:13 ` Kees Cook
2012-03-29 18:14 ` 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=20120327172133.GB10142@thunk.org \
--to=tytso@mit.edu \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
/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