Hi,
In addition to
<http://www.gnu.org/software/hurd/open_issues/crash_server.html>, it
seems that $CRASHSERVER isn’t honored, as suggested some time ago [0],
or perhaps the observations below are a side effect of another problem:
--8<---------------cut here---------------start------------->8---
l...@flubber:~$ cat > t.c
int main (int argc, char *argv[]) { *((char *) 0) = 0; return 0; }
l...@flubber:~$ gcc t.c
l...@flubber:~$ unset CRASHSERVER
l...@flubber:~$ ./a.out
Segmentation fault
l...@flubber:~$ export CRASHSERVER=/servers/crash-suspend
l...@flubber:~$ ./a.out
Segmentation fault (core dumped)
l...@flubber:~$ fsysopts /servers/crash-suspend
/hurd/crash --action=suspend --orphan-action=suspend
#
# Should have been suspended instead of dumping core.
l...@flubber:~$ fsysopts /servers/crash-kill
/hurd/crash --action=kill --orphan-action=kill
l...@flubber:~$ export CRASHSERVER=/servers/crash-kill
l...@flubber:~$ ./a.out
Segmentation fault
#
# I’d expect a message like “Killed”.
l...@flubber:~$ export CRASHSERVER=/foo/bar
l...@flubber:~$ ./a.out
Segmentation fault
#
# A warning would be nice.
--8<---------------cut here---------------end--------------->8---
In practice what’s the best way to debug a segfault?
Thanks,
Ludo’.
[0] http://www.mail-archive.com/debian-h...@lists.debian.org/msg01750.html
