> > > The 2.4-ac tree supports dumping core.$pid for the threads that actually
> > > died
> >
> > ... and these dumps are not reliable. Living thread may modify the
> > contents of dump as it's being written out. I.e. you are getting
> > false alarms - inconsistent data that was never there.
>
> That is mathematically insoluble. Think about an SMP system, you cannot stop
> the other thread in instantaneously small time
That's a separate problem - we can't catch the exact state of process
at the moment of death, indeed, but in theory we could make sure that
no changes happen while we write the thing out. As it is, coredump is not
only taken at some point after death, it doesn't correspond to state of
the thing at _any_ moment.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/