#111 segmentation fault


I get a number of spam messages through that cause bogofilter 1.2.1 to seg fault. I\\\'ve created the smallest test case file I can (6 bytes) that reliably segfaults bogofilter (attached).

darren@bacall ~ $ bogofilter -s < spamtest.txt
Segmentation fault


  • Darren Davison

    Darren Davison - 2010-07-03

    stupid sourceforge won't let me upload the 6 byte file (Error: file must be no larger than 256kb). Here are the contents;

    --start --

    -- end --

    (that's basically "\n\nfibr\n")

  • Matthias Andree

    Matthias Andree - 2010-07-05

    Hi Darren,

    I cannot reproduce this:

    $ printf '\n\nfibr\n' | valgrind -q build/src/bogofilter -vvvC
    X-Bogosity: Unsure, tests=bogofilter, spamicity=0.520000, version=1.2.2
    n pgood pbad fw U
    "fibr" 2 0.023256 0.018182 0.439492 -
    N_P_Q_S_s_x_md 0 0.000000 0.000000 0.520000
    0.017800 0.520000 0.375000

    Looks sane. No valgrind complaints. Might your database be corrupted?

    Can you give details on your bogofilter installation, and your computer? How did you install bogofilter, did you compile yourself (with what configure and make options), or did you use a package?

    Can you please:

    1) show the output of these commands:
    bogofilter -QQ
    bogofilter -V
    uname -a

    2) install the -dbg or -debuginfo (or similar, the naming depends on the distribution) symbol packages for bogofilter and possibly "gdb", or recompile bogofilter and use "make install" (not make install-strip!).

    Then type this, in sequence, without the bracketed text:

    printf '\n\nfibr\n' >/tmp/crash.txt
    gdb bogofilter
    run -s </tmp/crash.txt
    (this should print something about a segmentation fault)
    backtrace full
    (this should print lots of debug information)

    and post the output of backtrace full.

    Thank you.

  • Matthias Andree

    Matthias Andree - 2010-07-05

    Note: chances are that this crash stems from database corruption (bogoutil --db-verify can be used to check), hardware fault, or inconsistent installation, too. This is a guess, we don't yet know enough for a definitive assessment. Please help, see my previous comment.

  • Matthias Andree

    Matthias Andree - 2010-07-05
    • status: open --> open-works-for-me
  • Darren Davison

    Darren Davison - 2010-07-05

    hi, I've spent a little time going through some of this offline with David Relson and it does seem to be due to a fault in the database rather than the executable. Using a clean ~/.bogofilter/ doesn't reproduce the segfaults. I then rebuilt the db using -B and all of my current spam and ham corpuses, and again the segfault is not reproducible.

    David has a copy of my original wordlist.db and configs, along with outputs from ldd and other relevant info if further debugging is required. For now, I would close this issue and put it down to some oddity or damage in the original wordlist.db

    Thanks for the rapid responses.

  • Matthias Andree

    Matthias Andree - 2010-07-05
    • status: open-works-for-me --> closed-works-for-me
  • Matthias Andree

    Matthias Andree - 2010-07-05

    Apparent database corruption. Closing at submitter's suggestion.


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

Sign up for the SourceForge newsletter:

No, thanks