[CRIU] ARM: SIGSEGV in parasite code

[Chanho Park]

> I ran the script dump_test.sh 1000 times and I failed to reproduce the
> problem.

Hmm. I think this weird problem is occurred only to me.
Did you also use my criu tool?
If so, can you tell me your environment?

> Could you please reproduce the problem with the attached patch applied?
> This patch aborts the dumper if the SIGSEGV is intercepted so we may
> catch the SIGSEGV in the coredump.

Yeah. I've attached the coredump and log after applying your patch.
It might be also generated in the parasite code.
I also attached socket connection failed log between the tool and pie.
It didn't SIGSEGV signal.
But, dumping was failed and also infected program was killed.
IMHO the parasite code might have some weird problems.
Can you share your criu tool which compiles with static mode?

Thanks,

Best Regards,
Chanho Park
-------------- next part --------------
A non-text attachment was scrubbed...
Name: core
Type: application/octet-stream
Size: 704512 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20130612/03aca79b/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump.log
Type: application/octet-stream
Size: 4504 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20130612/03aca79b/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump_pie_connection_failed.log
Type: application/octet-stream
Size: 5633 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20130612/03aca79b/attachment-0005.obj>