Displaying 2 results from an estimated 2 matches for "imap_arg_nil".
Did you mean:
imap_arg_eol
2016 Dec 06
2
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
...0}, v = 0x85e4110,
v_modifiable = 0x85e4110}}, literal8 = 0}
(gdb) p args[4]
$5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str =
0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v
= 0x0, v_modifiable = 0x0}}, literal8 = 0}
(gdb) p args[5]
$6 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str =
0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v
= 0x0, v_modifiable = 0x0}}, literal8 = 0}
(gdb) p args[6]
$7 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str =
0x0, literal_size = 0, list = {arr = {buffer = 0x0,...
2016 Dec 06
2
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
On 06.12.2016 09:32, Toni Mattila wrote:
> Hi,
>
> On 05-Dec-16 20:28, Toni Mattila wrote:
>> Panicing stopped when all index files where deleted.
>
> It happens again in same user account, so rebuilding indexes didn't
> fix it.
>
> Here's bt full instead of just bt:
> #0 0x001d4402 in __kernel_vsyscall ()
> No symbol table info available.
> #1