On Thu, 16 Jul 1998, Brian White wrote:
Assuming that forking a kamakazi child is not an acceptable
solution, is there some way of capturing the image of the process from
the kernal?
Hmmm... That's interesting. Assuming there is no library/system call
to force a core dump,
PROTECTED], debian-user@lists.debian.org
Subject: Re: Dumping Core on Purpose
Resent-Date: 17 Jul 1998 15:29:25 -
Resent-From: debian-user@lists.debian.org
Resent-cc: recipient list not shown: ;
On Thu, 16 Jul 1998, Keith Beattie wrote:
C.J.LAWSON wrote:
I guess the next
On Thu, 16 Jul 1998, Vassilii Khachaturov wrote:
Yes. use CTRL-\
Nope, that would kill the program...
Maarten
_
| TU Delft, The Netherlands, Faculty of Information Technology and Systems |
|
On Thu, 16 Jul 1998, Stephen J. Carpenter wrote:
On Thu, Jul 16, 1998 at 12:13:44PM -0400, Brian White wrote:
Yes. use CTRL-\
I've never heard of that.
neither have II just tried it...it makes programs exit fast but
I have yet to produce a core dump with it
Actually,
On Thu, 16 Jul 1998, Stephen J. Carpenter wrote:
On Thu, Jul 16, 1998 at 12:13:44PM -0400, Brian White wrote:
Yes. use CTRL-\
I've never heard of that.
neither have II just tried it...it makes programs exit fast but
I have yet to produce a core dump with it
I tried it when I
On Thu, 16 Jul 1998, Keith Beattie wrote:
C.J.LAWSON wrote:
I guess the next logical question would be how to get a program to
backtrack and reload the core file .. and then contiue executing
Here's a wild shot at it...
Assuming that forking a kamakazi child is not an acceptable
On Thu, 16 Jul 1998, Brian White wrote:
Assuming that forking a kamakazi child is not an acceptable
solution, is there some way of capturing the image of the process from
the kernal?
Hmmm... That's interesting. Assuming there is no library/system call
to force a core dump, I could
Is there any way to make a program dump core and then continue execution?
Sorta like taking a snap-shot of the current program state.
Brian
( [EMAIL PROTECTED] )
Yes. use CTRL-\
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Is there any way to make a program dump core and then continue execution?
Sorta like taking a snap-shot of the current program state.
Brian
( [EMAIL PROTECTED] )
That's an interesting idea :). Let me see, I
Yes. use CTRL-\
I've never heard of that.
Actually, though... I was looking for the program to dump core when it
wanted (rather than at user request) and then be able to keep executing.
Brian
( [EMAIL PROTECTED] )
I guess the next logical question would be how to get a program to
backtrack and reload the core file .. and then contiue executing
--J.
On Thu, 16 Jul 1998, Brian White wrote:
Yes. use CTRL-\
I've never heard of that.
Actually, though... I was looking for the program to dump core
C.J.LAWSON wrote:
I guess the next logical question would be how to get a program to
backtrack and reload the core file .. and then contiue executing
That's what gdb is for.
--
see shy jo
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
On Thu, Jul 16, 1998 at 11:31:55AM -0400, Brian White wrote:
Is there any way to make a program dump core and then continue execution?
Sorta like taking a snap-shot of the current program state.
well I have made a program dump core on purpose...
how about...
kill(getpid(), SIGFPE);
the
On Thu, Jul 16, 1998 at 12:13:44PM -0400, Brian White wrote:
Yes. use CTRL-\
I've never heard of that.
neither have II just tried it...it makes programs exit fast but
I have yet to produce a core dump with it
Actually, though... I was looking for the program to dump core when it
C.J.LAWSON wrote:
I guess the next logical question would be how to get a program to
backtrack and reload the core file .. and then contiue executing
Here's a wild shot at it...
Assuming that forking a kamakazi child is not an acceptable
solution, is there some way of capturing the image
Assuming that forking a kamakazi child is not an acceptable
solution, is there some way of capturing the image of the process from
the kernal?
Hmmm... That's interesting. Assuming there is no library/system call
to force a core dump, I could fork a child and then make the child access
mem at
Brian White wrote:
Assuming that forking a kamakazi child is not an acceptable
solution, is there some way of capturing the image of the process from
the kernal?
Hmmm... That's interesting. Assuming there is no library/system call
to force a core dump, I could fork a child and then
On Thu, 16 Jul 1998, Brian White wrote:
: Assuming that forking a kamakazi child is not an acceptable
: solution, is there some way of capturing the image of the process from
: the kernal?
:
: Hmmm... That's interesting. Assuming there is no library/system call
: to force a core dump, I
In article [EMAIL PROTECTED],
Stephen J. Carpenter [EMAIL PROTECTED] wrote:
On Thu, Jul 16, 1998 at 12:13:44PM -0400, Brian White wrote:
Yes. use CTRL-\
I've never heard of that.
neither have II just tried it...it makes programs exit fast but
I have yet to produce a core dump with it
20 matches
Mail list logo
