#112 Process /usr/bin/bogofilter was killed by signal 11 (SIGSEGV


As the Fedora package maintainer I got a bug report about a bogofilter crash. See https://bugzilla.redhat.com/show_bug.cgi?id=626131


  • Tero Koskinen

    Tero Koskinen - 2010-08-24

    Hi, original author of that Fedora bogofilter crash bug here,

    The database in question is originally from OpenBSD/i386 with bogofilter 1.1.6.
    I think I have successfully used the database on OpenBSD/amd64 also, but not sure.

    To save time, I simply copied the database from OpenBSD when I started
    to use Sylpheed + bogofilter on Fedora 13/x86_64.

    So, the crash might be because of some database binary incompatibility between operating systems,
    different architectures (32-bit vs 64-bit), or bogofilter versions (1.1 vs 1.2).

    Of course, in the optimal case the filter should never crash and instead just report error if it finds invalid database.

  • David Relson

    David Relson - 2010-08-25

    As you say, copying the database and changing bogofilter versions should not cause a SIGSEGV. If you still have the message that crashed bogofilter, please post it so that I can try to reproduce and fix the problem.


  • Matthias Andree

    Matthias Andree - 2010-08-26
    • status: open --> closed-out-of-date
  • Matthias Andree

    Matthias Andree - 2010-08-26

    This was apparently pertinent only in bogofilter 1.2.0 and/or older, and got fixed in 1.2.2, see <https://bugzilla.redhat.com/show_bug.cgi?id=626131#c5>.

    Closing this bug.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks