Summary: | KMail crash with ldapkio resource enabled | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Michael Seiwert <michael.seiwert> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | sgh, tuju |
Priority: | NOR | ||
Version: | 1.8 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
valgrind trace
kmail backtrace |
Description
Michael Seiwert
2005-04-12 16:42:34 UTC
Created attachment 10593 [details]
valgrind trace
produced with:
valgrind --tool=addrcheck --num-callers=50 kmail --nofork 2>&1 | tee log
Created attachment 10594 [details]
kmail backtrace
kdepim is compiled with --enable-debug=full
Very good valgrind log, thanks. ==14774== by 0x39945849: KABC::ResourceLDAPKIO::enter_loop() (in /opt/kdehead/lib/libkabc_ldapkio.so.1.0.0) WAHHH. Using enter_loop is a very very bad idea, in case anyone still had doubts about that. If ldapkio's loading is async, kabc should load it async, instead of having to emulate sync from async using the very dangerous enter_loop. Tobias, is this possible? It this allso what happenens when kmail crashes when entering a recipient in a new email? Hi! I Have the same problem. Crashing of Kmail when adding a recipient to the TO: or CC: or BCC: fields, and during the LDAP lookup. My Kmail version is 1.12.1 on KDE 4.3.1, and the previous version had'nt this problem.... For me it is fixed in 4.3.4 Please close this bug. Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding |