[Aide] Segmentation fault

[Morgan Walker]

Did we ever get a diagnosis on the bt for the segmentation fault?

 

Thanks,

 

Morgan

 

Morgan Walker
Systems Administrator/Engineer
M*CAM, Inc.
Omni Business Center

210 Ridge-McIntire Rd., Suite 300

Charlottesville, VA 22903
434.979.7240 x311 

 

http://www.m-cam.com <http://www.m-cam.com>  
=========================================================
This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information.  Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you. 
=========================================================

________________________________

From: aide-bounces at cs.tut.fi [mailto:aide-bounces at cs.tut.fi] On Behalf
Of Morgan Walker
Sent: Monday, March 13, 2006 3:58 PM
To: Richard van den Berg
Cc: aide at cs.tut.fi
Subject: Re: [Aide] Segmentation fault

 

I ran the following:  gdb /usr/bin/aide.real 

 

Here is the output:

 

GNU gdb 6.4-debian

Copyright 2005 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you
are

welcome to change it and/or distribute copies of it under certain
conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB.  Type "show warranty" for
details.

This GDB was configured as "sparc-linux-gnu"...(no debugging symbols
found)

Using host libthread_db library "/lib/libthread_db.so.1".

 

(gdb) run --check

Starting program: /usr/bin/aide.real --check

warning: shared library handler failed to enable breakpoint

File database must have one db_spec specification

 

Program received signal SIGSEGV, Segmentation fault.

0x0002034c in ?? ()

 

(gdb) bt

#0  0x0002034c in ?? ()

#1  0x0000000c in ?? ()

Previous frame identical to this frame (corrupt stack?)

(gdb)

 

Hope this helps, thanks again.

 

Regards,

 

Morgan

 

Morgan Walker

Systems Administrator/Engineer

M*CAM, Inc.

Omni Business Center

210 Ridge-McIntire Rd., Suite 300

Charlottesville, VA 22903

434.979.7240 x311 

 

 

http://www.m-cam.com 

=========================================================

This message, including any attachments, is intended solely for the use

of the named recipient(s) and may contain confidential and/or

privileged information.  Any unauthorized review, use, disclosure or

distribution of this communication(s) is expressly prohibited.

If you are not the intended recipient, please contact the sender by

reply e-mail and destroy any and all copies of the original message.

Thank you. 

=========================================================

 

-----Original Message-----
From: Richard van den Berg [mailto:richard at vdberg.org] 
Sent: Monday, March 13, 2006 3:46 PM
To: Morgan Walker; Aide user mailinglist
Subject: Re: [Aide] Segmentation fault

 

Morgan Walker wrote:

> I am using aide-0.11.  I am not sure how to use gdb to run aide,
however

> I will attempt to figure that out,

 

I am not sure about the debian package, but you should be able to run 

something like: gdb /usr/bin/aide.real

and then inside gdb: run --check

When the seg fault occurs, type: bt

 

> database=file:/var/lib/aide/aide.db

> database_out=file:/var/lib/aide/aide.db.new

> 

> # Change this to "no" or remove it to not gzip output

> # (only useful on systems with few CPU cycles to spare)

> gzip_dbout=yes

 

It looks like your database at /var/lib/aide/aide.db is corrupted. It 

should be a gzipped file which starts out like this:

 

@@begin_db

# This file was generated by Aide, version 0.11

# Time of generation was 2006-03-05 01:15:26

@@db_spec

 

Still, aide should not seg fault when it encounters a corrupted aide.db.


Please send the result from the gdb back trace.

 

Sincerely,

 

Richard van den Berg

 

PS: do not forget to Cc the list when replying

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.cs.tut.fi/pipermail/aide/attachments/20060315/f70e24f4/attachment-0001.html