[CRIU] BUG: CRIU corrupt floating point state after checkpoint
Diyu Zhou
zhoudiyupku at gmail.com
Tue Oct 1 01:43:43 MSK 2019
The problem indeed goes away.
Do you have any insight why the corruption goes? As far as I can tell, the only
two bugs in the original code is the calloc and the thread worker function does
not return. After I have fixed these two bugs, with the original code,
the corruption is still there.
On Mon, Sep 30, 2019 at 2:05 AM Cyrill Gorcunov <gorcunov at gmail.com> wrote:
>
> On Fri, Sep 27, 2019 at 09:09:16AM -0700, Diyu Zhou wrote:
> > Thanks for pointing that out. It is indeed an embarrassing bug.
> >
>
> After modifying sources (to fix the issue with memory allocation)
> and using explicit pid instead of `ps` output it doesnt trigger
> anymore.
>
> Could you please use the archive I'm attaching to verify if it
> stop faulting for you?
>
> Please note there is a symlink to criu itself inside sources
> so adjust it the way it would point to your criu instance.
>
More information about the CRIU
mailing list