> [EMAIL PROTECTED]:/tmp$ ./crash
> Segmentation fault (core dumped)
> [EMAIL PROTECTED]:/tmp$ showtrans /servers/crash
> /hurd/symlink crash-suspend
> [EMAIL PROTECTED]:/tmp$ showtrans /servers/crash-suspend
> /hurd/crash --suspend
Strange.
Well, attach gdb to the cras
> [EMAIL PROTECTED]:/tmp$ ./crash
> Segmentation fault (core dumped)
> [EMAIL PROTECTED]:/tmp$ showtrans /servers/crash
> /hurd/symlink crash-suspend
> [EMAIL PROTECTED]:/tmp$ showtrans /servers/crash-suspend
> /hurd/crash --suspend
Strange.
Well, attach gdb to the crash server and see what it
Roland McGrath <[EMAIL PROTECTED]> writes:
>> Well, sometimes I just get coredumps with these settings. Is this
>> possible and am I doing something really stupid here or is this a bug?
>
> Could be neither. See --help: --suspend => --action=suspend,
> and the default --orphan-action=core-file r
Roland McGrath <[EMAIL PROTECTED]> writes:
>> Well, sometimes I just get coredumps with these settings. Is this
>> possible and am I doing something really stupid here or is this a bug?
>
> Could be neither. See --help: --suspend => --action=suspend,
> and the default --orphan-action=core-file r
I have /hurd/crash, which is a symlink to crash-suspend (Which is
started as "/hurd/crash --suspend").
Well, I just assume that means that whenever a process segfault it
will wait until I can attach gdb to it.
Well, sometimes I just get coredumps with these settings. Is this
po
> Well, sometimes I just get coredumps with these settings. Is this
> possible and am I doing something really stupid here or is this a bug?
Could be neither. See --help: --suspend => --action=suspend,
and the default --orphan-action=core-file remains in effect.
Perhaps when you get a core file,
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes:
> haven't looked into this at all, but thought that I might report it
> anyway and check if it is indeed the intended behavior.
>
> If /servers/crash is not a core dumping crash server (i.e is either
> --kill or --suspend), then doing `gcore PID' wil
Hi,
haven't looked into this at all, but thought that I might report it
anyway and check if it is indeed the intended behavior.
If /servers/crash is not a core dumping crash server (i.e is either
--kill or --suspend), then doing `gcore PID' will do whatever the
crash server is currently. That is
