Bug 118197 - Segmentation fault in sa-learn
Summary: Segmentation fault in sa-learn
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: 1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-13 10:06 UTC by Adam Huffman
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-05-21 23:37:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Debug output of crashing sa-learn (with mail address censored) (6.88 KB, text/plain)
2004-03-13 10:10 UTC, Adam Huffman
no flags Details

Description Adam Huffman 2004-03-13 10:06:11 UTC
Description of problem:
Noticing that spamassassin didn't seem to be checking some incoming
mail at all, I moved that mail to a separate folder and ran sa-learn
on it.  Sa-learn appears to be crashing when processing some of these
messages.

Version-Release number of selected component (if applicable):
2.63-0.2

How reproducible:
Every time

Steps to Reproduce:
1. run sa-learn on a folder of spam
2.
3.
  
Actual results:
sa-learn crashes with a segmentation fault

Expected results:
sa-learn processes the messages

Additional info:

Comment 1 Adam Huffman 2004-03-13 10:10:18 UTC
Created attachment 98509 [details]
Debug output of crashing sa-learn (with mail address censored)

Comment 2 Warren Togami 2004-05-20 08:21:28 UTC
It would really help for the developers to debug and fix this if you
can attach an isolated mbox file that causes the crash.  See if you
can cut pieces out that are unrelated to the crash, as well as
anything for privacy reasons.

Comment 3 Adam Huffman 2004-05-21 07:54:53 UTC
I did talk with a couple of developers on IRC.  In the end, I deleted
my SA installation and started from scratch.  That seems to have
solved the problem.  It's likely that the Bayesian database had become
corrupted.

Mail was becoming unusable again so I couldn't wait any longer for a fix.

If this reappears, I'll reopen the bug.  


Note You need to log in before you can comment on or make changes to this bug.