On Tue, 2005-06-07 at 20:52 -0700, Doug Luce wrote:
When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong?
Here's where a SIGABRT happens:
280 return array->buffer->used / array->element_size;
This is the stack trace:
(gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0, idx_r=0x11ffe828) at ../../src/lib/array.h:280 #1 0x120058dcc in _view_lookup_ext_full (view=0x1200c0db0, seq=0, ext_id=0, map_r=0x11ffe898, data_r=0x11ffe8a0) at mail-index-view.c:395
I can't really see how this could happen.. You can reproduce this every time? Does it matter what the source or destination mailboxes are? Could you show output of these commands in gdb:
p *map p *map.ext_id_map p *map.ext_id_map.buffer
(gdb) s
Program received signal SIGABRT, Aborted. 0x130247908 in kill () from /lib/libc.so.5
SIGABRT? I was expecting SIGSEGV. Does it write something to log? Is the backtrace different after the SIGABRT?