[Bug 227252] Re: The generated binaries always crash
In addition to the mmap_min_addr change above, you also need to set /proc/sys/vm/vdso_enabled to either 0 (no vDSO) or 2 (compatibility vDSO mode - mapping to 0x). I'd recommend setting it to 2 for performance. The default is 1 which maps the vDSO page somewhere in the user process's address space, and that's not being restored correctly. I'm not entirely sure what it's unhappy about it still, but at least this suffice as a workaround for now. (Additionally, you can actually save a image with the default of vdso_enabled=1, so long as you restore it with vdso_enabled=2). -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
cryopid has been recently removed from Ubuntu and Debian, so I'm closing ths bug report for now. Please reopen if you can provide further informations. Thank you in advance! ** Changed in: cryopid (Ubuntu) Status: Confirmed = Won't Fix -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
Could you please check if recent kernels work with cryopid? -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
Some mmap restrictions recently went into the kernel to help mitigate null-pointer deref bugs and other classes of exploits. Running sudo sh -c 'echo 4096 /proc/sys/vm/mmap_min_addr' should allow cryopid to get past this stumbling block. Alternately, the resumer code should be put at a higher address. Ubuntu ships with a default mmap_min_addr of 64K (0x1). It shouldn't hurt to put the resumer there instead. -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
** Changed in: cryopid (Ubuntu) Importance: Undecided = Medium -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
I figured out that the binaries crash only with certain kernel configs. In particular, I changed a few things in the Processor type and features section of the kernel config and now the generated binaries restart all right. I've changed three or four things at the same time and am not sure which one is responsible for the behavior, but attached both a working and a not working configuration. The kernel I'm using now is 2.6.25.7 but it's the same with some older kernels as well (2.6.20.15 certainly). I've found out about this by comparing the kernel configs for the kernels in 7.04 (binaries working) and 8.04 (not working). If anybody is willing to narrow down the kernel option causing this, they're more than welcome. ** Attachment added: Kernel config that works http://launchpadlibrarian.net/15763881/config-working -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
** Attachment added: Kernel config that doesn't http://launchpadlibrarian.net/15763896/config-NOT-working -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
I attached a wrong .config file above, this is the one that freeze binaries truly work with. This one turns the Tickless system High resolution timer support options off. It seems this is really necessary for the binaries to work. ** Attachment added: Kernel config that REALLY works http://launchpadlibrarian.net/15772570/config-working -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
I've experienced this. This happens only in Ubuntu 8.04 though, apparently due to newer kernels. The binary generated by freeze works OK with older kernels (definitely with 2.6.20-15-386), even if it was saved with a new kernel (2.6.24-16-generic). It may be that (1) the kernel config was changed between the two kernel versions, or that (2) freeze just doesn't work with the new kernels. What a pity it would be -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
I've independently discovered this and then found this bug. Confirming. I'm using exactly the same version of cryopid as Marco on x86. Makes no difference whether the -l option is given. ** Changed in: cryopid (Ubuntu) Status: New = Confirmed -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
I've found `strace /tmp/foo.frozen' is a good means of debugging. Here, I find one of the first things foo.frozen attempts, regardless of what program was frozen, is mmap2(0x1000, 57344, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = -1 EACCES (Permission denied) and we suffer a SIGSEGV. Running it as `sudo strace /tmp/foo.frozen' means it gets past this and can either successfully run, or crash for program-specific reasons. -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227252] Re: The generated binaries always crash
** Attachment added: Example program for testing cryopid http://launchpadlibrarian.net/14254212/ciao.c -- The generated binaries always crash https://bugs.launchpad.net/bugs/227252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
