Date: Thu, 20 Jun 2002 12:39:55 +0300 From: "Andrey Simonenko" <simon@comsys.ntu-kpi.kiev.ua> To: <ticso@cicely.de> Cc: <freebsd-hackers@freebsd.org> Subject: Re: Is it possible to store process state and then restore process Message-ID: <00d501c2183e$6f35a1e0$6d36120a@pm5149> References: <006401c21793$30721750$6d36120a@pm5149> <20020619141241.GO43253@cicely5.cicely.de.lucky.freebsd.hackers> <007501c21839$3caabc60$6d36120a@pm5149> <20020620092343.GU43253@cicely5.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Bernd Walter" <ticso@cicely5.cicely.de> To: "Andrey Simonenko" <simon@comsys.ntu-kpi.kiev.ua> Cc: <ticso@cicely.de>; <freebsd-questions@freebsd.org> Sent: Thursday, June 20, 2002 12:23 PM Subject: Re: Is it possible to store process state and then restore process > But that's the main problem: > You almost ever have shared filedescriptors (stdin, ...). > Such a mechanism wouldn't work without the application support unless > you build the complete support into the kernel. I try to consider very simple example, because my knowledges in this field are limited. > You could dump core and convert the dump into an object format. That is, can I say that it is possible with FreeBSD to dump process image (allocated memory, changed data segment, stack, PCB, ...) to a file and then restore this image? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00d501c2183e$6f35a1e0$6d36120a>