BIND 10 #1672: b10-resolver crashing with status 11
BIND 10 Development
do-not-reply at isc.org
Tue Feb 14 08:18:40 UTC 2012
#1672: b10-resolver crashing with status 11
-------------------------------------+-------------------------------------
Reporter: | Owner:
Jeffry A. Spain | Status: new
Type: | Milestone: New Tasks
defect | Resolution:
Priority: major | Sensitive: 0
Component: | Sub-Project: DNS
resolver | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: High |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by vorner):
Hello
Replying to [comment:1 jreed]:
> I assume exit status 11 is EAGAIN or EWOULDBLOCK on this Ubuntu Linux
system.
No. This is the exit code/return status/$? of the process. That has
nothing to do with errno codes. I wrote a small program to decode the
value, assuming that ubuntu doesn't have different status encoding from
gentoo:
{{{#!C
#include <sys/types.h>
#include <sys/wait.h>
#include <stdio.h>
int main(int argc, const char ** argv) {
printf("Exited: %d, Exit status: %d, Signaled: %d, Signal: %d\n",
WIFEXITED(11), WEXITSTATUS(11),
WIFSIGNALED(11), WTERMSIG(11));
return 0;
}
}}}
The output is:
Exited: 0, Exit status: 0, Signaled: 1, Signal: 11
So, the problem is SEGFAULT somewhere in the code. We might want to add
the decoding of the exit code into the boss sometime, the number is not
really helpful.
Jaspain, would it be too much to ask if you happen to have core dumps
enabled? A backtrace from gdb could be very helpful (KDE has a really
useful thingie, if a program crashes, it tries to get the backtrace
automatically and detects if it could be useful and asks the user to send
it, we probably want to think about some simple way for this as well).
Thank you
--
Ticket URL: <http://bind10.isc.org/ticket/1672#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list