From: Michael Ellerman <michael@ellerman.id.au>
To: Dave Jones <davej@redhat.com>
Cc: trinity@vger.kernel.org
Subject: Re: wtf bug of the day.
Date: Mon, 01 Jul 2013 18:18:51 +1000 [thread overview]
Message-ID: <1372666731.31133.2.camel@concordia> (raw)
In-Reply-To: <20130629022420.GA20808@redhat.com>
On Fri, 2013-06-28 at 22:24 -0400, Dave Jones wrote:
> I've beem holding off on cutting a new release of trinity until I've nailed
> this one last bug[1].
>
> When it happens, the watchdog process is in Z state, and the child processes
> are all blocked on sockets (and no progress is made because the watchdog died).
>
> In the one case I've managed to catch a core from the watchdog, it makes no damn sense..
>
> Program terminated with signal 8, Arithmetic exception.
> #0 check_shm_sanity () at watchdog.c:47
> if (shm->running_childs == 0)
>
> what the hell does that even mean ?
>
> 'shm' is valid, shm->running_childs is '4'.
>
> Any ideas ?
You could add a SIGFPE handler and check whether it's coming from
another process or not.
Something like:
void sighandler(int signal, siginfo_t *siginfo, void *ucontext)
{
printf("Took signal %d\n", signal);
printf("Sent by process %d (uid %d)\n",
siginfo->si_pid, siginfo->si_uid);
}
struct sigaction sigfpe_action = {
.sa_sigaction = sighandler,
.sa_flags = SA_SIGINFO,
};
if (sigaction(SIGFPE, &sigfpe_action, NULL)) {
perror("sigaction");
return 1;
}
cheers
prev parent reply other threads:[~2013-07-01 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 2:24 wtf bug of the day Dave Jones
2013-06-29 6:31 ` Jann Horn
2013-07-01 8:18 ` Michael Ellerman [this message]
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=1372666731.31133.2.camel@concordia \
--to=michael@ellerman.id.au \
--cc=davej@redhat.com \
--cc=trinity@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