| Summary: | crash opening misconfigured/malformatted mail | ||
|---|---|---|---|
| Product: | [Applications] kmail | Reporter: | Axel Braun <axel.braun> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bjoern |
| Priority: | NOR | ||
| Version: | 1.9.1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | output from carhsmanager | ||
Please attach the problematic mail to the report if possible, as well as a backtrace from the crash. I attach the crash report, but will send the mail by PM, because the content is confidential. To whom shall I send it? Created attachment 16114 [details]
output from carhsmanager
Backtrace contains no useful information. The section that you pasted from the email shows that it is not a MIME email: that's UUencode that you pasted. We cannot do much without the mail In comment #2 I was asking for a PM-address to send the mail to, as it contained confidential stuff. I have localized the problematic mail, but it looks as the problem was fixed 'drive-by' in between. Thanks for taking care. |
Version: 1.9.1 (using KDE 3.5.2 Level "a" , SUSE 10.0 UNSUPPORTED) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.13-15.8-default I received a mail which has obviously a faulty MIME-section in it. The mail is displayed properly, but when trying to view the mail source code, Kmail crashes. There are not too may dsbugging information available, so if one of the developers could tell me how to do a post-mortem analysis with gdb or something....thanks. The section causing problems starts as clear text with begin 666 060515-BvsB.pdf M)5!$1BTQ+C0-)>+CS],-"C$P(# @;V)J(#P\+TQI;F5A<FEZ960@,2],(#4P M,# W-R]/(#$S+T4@-#DQ-#<T+TX@,2]4(#0Y.3@S,"]((%L@-# Q-38@,C,T M,UT^/@UE;F1O8FH-(" @(" @(" @(" @#0IX<F5F#0HQ," Q ..and so on.