Messages in this thread | | | Date | Tue, 03 Sep 2013 16:17:22 +0530 | From | Janani Venkataraman <> | Subject | Re: RFD: Non-Disruptive Core Dump Infrastructure |
| |
On 09/03/2013 04:01 PM, Pavel Emelyanov wrote: > On 09/03/2013 12:39 PM, Janani Venkataraman wrote: >> Hello, >> >> We are working on an infrastructure to create a system core file of a specific >> process at run-time, non-disruptively. It can also be extended to a case where >> a process is able to take a self-core dump. > > This is very close to what we're trying to do in CRIU. And although image files > containing info about processes are not ELF files, an ability to generate ELF-cores > out of existing CRIU images is one of the features that we were asked for. > >> 2) CRIU Approach : >> >> This makes use of the CRIU tool and checkpoints when a dump is called, collects >> the required details and continues the running process. >> * A self dump cannot be initiated using the command line CRIU which is similar >> to the limitation of gcore. > > This is something we're trying to fix at the moment, as people ask for 'self-dump' > ability as well. We plan to have this implemented in v0.8 (the v0.7 is coming out > today/tomorrow) in about a month. > > I can shed more light on this, if required. > >> * A system call to do the same is being implemented which would help us create >> a self dump.The system call is not upstream yet. We could explore that option as >> well. > > Thanks, > Pavel > Hi,
I would like to know more about the "self-dump" ability of CRIU. This is the implementation using system calls if I am not wrong.
Thanking You. Regards, Janani Venkataraman
| |