mu coredump

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run either 'mu find' or 'mu cfind' 
2.(see dump files)
3.

What is the expected output? 
Output of find/cfind.

What do you see instead?
Coredump

What version of the product are you using? On what operating system?
mu (mail indexer/searcher) version 0.9.9.6
Arch Linux, kernel 3.16.3-1 x86_64

Please provide any additional information below.
Happens every time on command line.
Searches within mu4e work fine.
Dumps attached
Note on the cfind dump that on the last line, just before "Aborted" it shows 
the correct (?) output "Jay Dresser"

Original issue reported on code.google.com by jtg...@gmail.com on 3 Oct 2014 at 5:47

Attachments:

• mu-find.dump
• mu-cfind.dump

[GoogleCodeExporter]

Hmmm... would it be possible to create gdb backtrace from this? 

Something like:
$ gdb --args mu find hello
run
backtrace

Thanks.

Original comment by digg...@gmail.com on 5 Oct 2014 at 3:26

[GoogleCodeExporter]

Sure.

Program received signal SIGABRT, Aborted.
0x00007ffff62ce967 in raise () from /usr/lib/libc.so.6
(gdb) backtrace
#0  0x00007ffff62ce967 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff62cfd3a in abort () from /usr/lib/libc.so.6
#2  0x00007ffff630e413 in __libc_message () from /usr/lib/libc.so.6
#3  0x00007ffff6393a97 in __fortify_fail () from /usr/lib/libc.so.6
#4  0x00007ffff6393a60 in __stack_chk_fail () from /usr/lib/libc.so.6
#5  0x000000000042b331 in ?? ()
#6  0x000000000040c320 in ?? ()
#7  0x000000000040cbcb in ?? ()
#8  0x000000000041009b in ?? ()
#9  0x0000000000409d5b in ?? ()
#10 0x00007ffff62bb040 in __libc_start_main () from /usr/lib/libc.so.6
#11 0x0000000000409f07 in ?? ()
(gdb) 

Original comment by jtg...@gmail.com on 5 Oct 2014 at 3:44

[GoogleCodeExporter]

Thanks -- one more request: could you try and get the same backtrace but with 
an unoptimized build? I.e.

./configure CFLAGS="-O0 -ggdb" && make clean && make 

Original comment by digg...@gmail.com on 12 Oct 2014 at 10:35

[GoogleCodeExporter]

Puzzling

I installed mu (I use packer) and aborted during the compile.
I then compiled with the command line you gave.
There was no error in gdb and it returned results normally.
I ran without gdb and it was normal.

I noticed during install that it complained about conflict with mu-git so I 
guess I had the git version originally.
I then installed the git version to see if that was the problem.
It now also works correctly.

I can't explain it but the bug seems to have gone away in both the normal and 
git versions.
Have you done a release since I reported the bug?

In any case, thanks, it seems ok for now. I'll do more testing.

Original comment by jtg...@gmail.com on 13 Oct 2014 at 6:54