Bug 2725 - Crash while loading new mail
Summary: Crash while loading new mail
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.8.1
Hardware: PC Linux
: P3 normal
Assignee: users
Depends on:
Reported: 2012-08-24 08:38 CEST by rafmav
Modified: 2012-08-26 01:25 CEST (History)
0 users

See Also:

bug report (4.65 KB, text/plain)
2012-08-24 08:38 CEST, rafmav
no flags Details
running claws-mail in gdb (6.07 KB, text/x-log)
2012-08-26 00:47 CEST, rafmav
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rafmav 2012-08-24 08:38:27 CEST
Created attachment 1150 [details]
bug report
Comment 1 Ricardo Mones 2012-08-24 08:46:22 CEST
The backtrace is useless as it comes from striped binaries. 

Read http://www.claws-mail.org/faq/index.php/Debugging_Claws and try to provide a useful backtrace. A description of how this happened would be also appreciated.
Comment 2 rafmav 2012-08-24 19:23:12 CEST
After clicking on the button to get the new mail from the internet (removed from the server site). Mail is downloaded but unreadable because the program shutdown.

gdb claws-mail
Reading symbols from /usr/bin/claws-mail...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/claws-mail 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3200.4-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[New Thread 0x7fffe7be9700 (LWP 14198)]
[Thread 0x7fffe7be9700 (LWP 14198) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff43262aa in __strchr_sse2 () from /lib/libc.so.6
(gdb) quit
A debugging session is active.

	Inferior 1 [process 14185] will be killed.

Quit anyway? (y or n) y
Comment 3 Paul 2012-08-24 19:46:53 CEST
downgrading severity because this only happens to you. Please attach a useful backtrace as requested in comment #1
Comment 4 rafmav 2012-08-26 00:47:44 CEST
Created attachment 1151 [details]
running claws-mail in gdb
Comment 5 rafmav 2012-08-26 01:25:16 CEST
Under Archlinux, the version of claws-mail I used was 3.8.1 from pacman. The installation from archlinux AUR is wrong to (bad PKGBUILD ?? huh?). I used  Installed 3.8.1cvs35 directly from claws-mail site instead: the bug disappeared.