#68 SIGBUS on sparc64

0.13
open
nobody
5
2008-01-18
2008-01-18
Marc Haber
No

Hi,

this is Debian Bug #152203, which is ancient, but seems to be reproduced on today's systems. See http://bugs.debian.org/152203:

Hello

Everytime I execute "aide --init" on sparc64 aide is killed by a SIGBUS. It
seams this happens the first time, it tries to write real data to aide.db.new.

Original bug reporter writes:
Here are the last lines
of "aide --init --verbose=255":
| Checking /var/lib/xdm for match
| File /var/lib/xdm does not match
| db_init 0
| Opening file "/var/lib/aide/aide.db.new" for w+
| db_out is nonnull /var/lib/aide/aide.db.new
| Caught SIGBUS/SIGSEGV
| Caught SIGBUS/SEGV. Exiting
| Aborted

aide.db.new remains as a 10 Bytes large file.

And here is the backtrace:
| #0 0x0003a77c in md_enable ()
| #1 0x0003a7f8 in gcry_md_enable ()
| #2 0x0001e524 in do_md (file_lst=0xfd6f8, conf=0xfa098) at do_md.c:142
| #3 0x00024124 in main (argc=2, argv=0xeffffd64) at aide.c:406

Maybe a problem with libmhash2?

Discussion

  • Marc Haber

    Marc Haber - 2008-01-18

    Logged In: YES
    user_id=406900
    Originator: YES

    This may be a mhash issue, see http://bugs.debian.org/429180.

     
  • Richard van den Berg

    Logged In: YES
    user_id=330646
    Originator: NO

    Does the same problem occur on both etch (libmhash2 0.9.7-1) and lenny (libmhash2 0.9.9-1)?

     

Log in to post a comment.