* What could cause siginfo_t.si_addr to always be NULL?
@ 2013-08-27 10:48 Mike Hommey
0 siblings, 0 replies; only message in thread
From: Mike Hommey @ 2013-08-27 10:48 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-08-27 10:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-27 10:48 What could cause siginfo_t.si_addr to always be NULL? Mike Hommey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox