Re: Repeated crashes on x86-64
On Tuesday, 22 March 2005 at 10:52, Mads Martin Joergensen wrote:
> Hey all,
>
> Here's another backtrace from a dumped core from mutt-1.5.9[*].
> It got better with 1.5.9, and this usually happens at night when it's
> just sitting there.
>
> #0 0x00002aaaab40de79 in raise () from /lib64/tls/libc.so.6
> #1 0x00002aaaab40f48f in abort () from /lib64/tls/libc.so.6
> #2 0x00002aaaab4425d3 in __fsetlocking () from /lib64/tls/libc.so.6
> #3 0x00002aaaab447153 in malloc_usable_size () from /lib64/tls/libc.so.6
> #4 0x00002aaaab449e89 in free () from /lib64/tls/libc.so.6
> #5 0x00002aaaab44ad50 in realloc () from /lib64/tls/libc.so.6
> #6 0x000000000045c2bd in safe_realloc (ptr=0xd98228, siz=<value optimized
> out>)
> at lib.c:109
not sure what's going on with the siz parameter. Anyone?
> #7 0x00000000004385ef in mx_alloc_memory (ctx=0xd981c0) at mx.c:1587
that line number is odd. Maybe a make clean is in order?
But what's ctx->hdrmax here?
one more thing - can you see if this happens if you move /lib64/tls
out of the way? It's kind of a wild guess but I don't entirely trust
the tls libraries.
> #8 0x0000000000477753 in imap_read_headers (idata=0x60c5b0, msgbegin=701,
> msgend=704) at message.c:118
> #9 0x0000000000472fcd in imap_cmd_finish (idata=0x60c5b0) at command.c:266
> #10 0x0000000000473c9b in imap_check_mailbox (ctx=<value optimized out>,
> index_hint=<value optimized out>, force=<value optimized out>) at
> imap.c:1168
> #11 0x000000000041a0ec in mutt_index_menu () at curs_main.c:479
> #12 0x000000000043109c in main (argc=1, argv=0x7fffffa18018) at main.c:940
> #13 0x00002aaaab3fc54a in __libc_start_main () from /lib64/tls/libc.so.6
> #14 0x00000000004061fa in _start () at start.S:113