URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=17319>
Summary: /hurd/crash --suspend doesn't work
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Friday 08/04/06 at 16:14
Category: Hurd Servers
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Reproducibility: Every Time
Size (loc): None
Planned Release: None
Effort: 0.00
_______________________________________________________
Details:
`/hurd/crash --suspend' is usually running as a server on
`/servers/crash-suspend' and may be linked to from `/servers/crash' to
actually use it.
It's meant to suspend a crashed process, i.e. keep it in a frozen state in
memory (as opposed to dumping a core file) to make it attachable and
debuggable by gdb.
Unfortunately this doesn't work:
#v+
[EMAIL PROTECTED]:/var/tmp $ cat > crash.c
int main (void) { return *(int *) 0; }
[EMAIL PROTECTED]:/var/tmp $ gcc crash.c
[EMAIL PROTECTED]:/var/tmp $ ./a.out
Segmentation fault (core dumped)
[EMAIL PROTECTED]:/var/tmp $ ls -l core
-rw------- 1 thomas root 16912384 Jun 15 20:43 core
[EMAIL PROTECTED]:/var/tmp $ ls -l /servers/crash
lrwxr-xr-x 1 root root 13 Jun 15 20:42 /servers/crash -> crash-suspend
[EMAIL PROTECTED]:/var/tmp $ showtrans /servers/crash-suspend
/hurd/crash --suspend
#v-
According to Roland it has been working ``in the past'' (``Long before core
dumping ever worked at all.'') and he also added that ``the crash server is
one of the easier ones to debug with gdb.''
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=17319>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
