From: Mike Hommey <mh@glandium.org>
To: linux-kernel@vger.kernel.org
Subject: What could cause siginfo_t.si_addr to always be NULL?
Date: Tue, 27 Aug 2013 19:48:40 +0900 [thread overview]
Message-ID: <20130827104840.GA16959@glandium.org> (raw)
Hi,
We're running into an interesting issue with Firefox on Android, in
which a segfault signal handler always gets a value of 0 for
siginfo_t.si_addr. The most intesting part is that this only happens on
a few devices/android version combinations. Catching a segfault in gdb
also shows the problem in $_siginfo, which suggests this would be the
kernel doing something weird. Thus my question, what in the kernel could
cause this behavior?
Cheers,
Mike
reply other threads:[~2013-08-27 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130827104840.GA16959@glandium.org \
--to=mh@glandium.org \
--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