Re: 24.2 crash

[Dmitry Antipov]

On 03/19/2013 07:49 PM, Kevin Layer wrote:

> > > 3. Your crash is likely caused by the heap corruption; try to find
> > >     the reason by running _undumped_ (src/temacs) executable under
> > >     valgrind, e.g. valgrind --tool=memcheck ./src/temacs [...].
>
> I ran this.  Lots of output.  What do you want me to do with it?

Collect an output with --log-file=FILE.txt valgrind option and check
FILE.txt for the messages like:

- Address 0xXXXXXXXX is not stack'd, malloc'd or (recently) free'd
- Address 0xXXXXXXXX is Y bytes before a block of size Z alloc'd
- Address 0xXXXXXXXX is Y bytes after a block of size Z alloc'd
- Invalid free() / delete / delete[] / realloc()

If you see something similar at least once, or final crash of the
valgrind itself, this is most likely a heap management error.

Anyway, compress FILE.txt (most probably xz gives the best result)
and send it to me.

Dmitry