[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

$CRASHSERVER not honored?

From: Ludovic Courtès
Subject: $CRASHSERVER not honored?
Date: Mon, 26 Apr 2010 16:20:30 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)


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---
ludo@flubber:~$ cat > t.c
int main (int argc, char *argv[]) { *((char *) 0) = 0; return 0; }
ludo@flubber:~$ gcc t.c
ludo@flubber:~$ unset CRASHSERVER
ludo@flubber:~$ ./a.out
Segmentation fault
ludo@flubber:~$ export CRASHSERVER=/servers/crash-suspend
ludo@flubber:~$ ./a.out
Segmentation fault (core dumped)
ludo@flubber:~$ fsysopts /servers/crash-suspend 
/hurd/crash --action=suspend --orphan-action=suspend
# Should have been suspended instead of dumping core.

ludo@flubber:~$ fsysopts /servers/crash-kill 
/hurd/crash --action=kill --orphan-action=kill
ludo@flubber:~$ export CRASHSERVER=/servers/crash-kill
ludo@flubber:~$ ./a.out 
Segmentation fault
# I’d expect a message like “Killed”.

ludo@flubber:~$ export CRASHSERVER=/foo/bar
ludo@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?


[0] http://www.mail-archive.com/debian-hurd@lists.debian.org/msg01750.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]