[CRIU] [PATCH 2/3] crit: add core-dump feature

[Ruslan Kuprieiev]

On 22.04.15 12:51, Pavel Emelyanov wrote:
> On 04/19/2015 09:50 PM, Ruslan Kuprieiev wrote:
>> crit core-dump is to be used to produce valid elf core dump
>> from criu images. It is already able to produce core dump that
>> is readable and can be used by objdump, readelf and gdb.
>> Still, it is not perfect and lacks some vma contents(vsyscall
>> and vvar) and some core notes are not fullfilled.
>>
>> It is also worth noting that for now only x86_64 architecture
>> is supported.
> But there's no such check in the crit code ;)

Oh, yes. Still planning to expand it to support all of them.
Could I send a patch on top of this set?

>> Signed-off-by: Ruslan Kuprieiev <kupruser at gmail.com>
>> ---
>>   crit                       |  18 +-
>>   pycriu/images/__init__.py  |   1 +
>>   pycriu/images/core_dump.py | 766 +++++++++++++++++++++++++++++++++++++++++++++
>>   pycriu/images/elf.py       | 526 +++++++++++++++++++++++++++++++
>>   4 files changed, 1310 insertions(+), 1 deletion(-)
>>   create mode 100644 pycriu/images/core_dump.py
>>   create mode 100644 pycriu/images/elf.py
> Are there ready bits for python for any of these? I've
> googled for pyelftools, isn't it what we need?

Nope, pyelftools are quite dumb and they don't match our needs.
I also tried using ctypesgen.py to generate ctypes structures from c 
headers,
but it is quite dumb and doesn't work in many cases, especially with 
such complicated
headers as for example procfs.h and there is no reason to bring it with us.
Well, it is kinda the same thing as it was with pb->json converters, all 
of them
are not ready for production and badly supported and distributed, so we 
need to
create our own.


>
> -- Pavel