"mu index" core dumping on Ubuntu 13.04, with version 0.9.9

[GoogleCodeExporter]

I can't seem to reproduce this, so this might be not be actionable.

I ran "mu index" three times:

During the first run, it core dumped.
During the second run, it core dumped.
On the third run (and subsequent), it ran successfully without error.

# mu -v
mu (mail indexer/searcher) version 0.9.9

This is using the standard install package available in Ubuntu 13.04.

I'm not sure what logs you'd want or need.

Grepping for mu in /var/log/syslog:

May  7 11:04:52 myhost kernel: [902908.222810] show_signal_msg: 42 callbacks 
suppressed
May  7 11:04:52 myhost kernel: [902908.222815] mu[26013]: segfault at 61 ip 
00007f0522f18d3c sp 00007fffc8fbbf40 error 4 in 
libxapian.so.22.5.0[7f0522e5d000+1d0000]

apport.log:

ERROR: apport (pid 26021) Tue May  7 11:04:53 2013: called for pid 26013, 
signal 11, core limit 0
ERROR: apport (pid 26021) Tue May  7 11:04:53 2013: executable: /usr/bin/mu 
(command line "mu index")
ERROR: apport (pid 26021) Tue May  7 11:04:53 2013: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 26021) Tue May  7 11:05:25 2013: wrote report 
/var/crash/_usr_bin_mu.0.crash
ERROR: apport (pid 26031) Tue May  7 11:06:06 2013: called for pid 26029, 
signal 6, core limit 0
ERROR: apport (pid 26031) Tue May  7 11:06:06 2013: executable: /usr/bin/mu 
(command line "mu index")
ERROR: apport (pid 26031) Tue May  7 11:06:06 2013: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 26031) Tue May  7 11:06:06 2013: apport: report 
/var/crash/_usr_bin_mu.0.crash already exists and unseen, doing nothing to 
avoid disk usage DoS

I'll happy post the crash logs from /var/crash/_usr_bin_mu.0.crash ONCE SOMEONE 
CONFIRMS that this isn't going to leak any personal data.

I don't care much about user name/machine names, but obviously my email is 
sensitive.

I can't reproduce this, so I'm not sure that there's much value in filing the 
bug, but I figure that something might be gleaned from it, or someone else who 
is regularly having this problem might speak up.

Thanks

Original issue reported on code.google.com by kmo...@gmail.com on 7 May 2013 at 4:43

[GoogleCodeExporter]

Hmmm, is still visible with later versions of mu? 

In any case, what you god try is use gdb, something like:

$ gdb --args mu index
GNU gdb (GDB) 7.6-debian
Copyright (C) 2013 Free Software Foundation, Inc.
[...]

now, press 'r'; mu index should run. When it crashes, enter 'bt'.
Then, copy-paste the output to this report. It's just text, so you
can verify it's not including any personal info.

Thanks.

Original comment by digg...@gmail.com on 3 Jun 2013 at 9:19

[GoogleCodeExporter]

Can't do anything with this...

Original comment by digg...@gmail.com on 29 Dec 2013 at 3:52

• Changed state: Invalid