argus malloc memory corruption error

[Carter Bullard]

Do you have valgrind ?

   # valgrind --leak-check=yes argus

Carter

On Aug 1, 2013, at 12:45 PM, Mike Iglesias <iglesias at uci.edu> wrote:

> On 08/01/2013 06:04 AM, Carter Bullard wrote:
>> Hey Mike,
>> One of the argus threads has died, and the ArgusOutput thread may still be running.  If you can turn on the development support, ( touch .devel; ./configure; make clean; make ) and run under gdb, we'll catch it.
>> 
>>   # gdb bin/argus
>>   (gdb) run -d      (Assuming your argus runs in daemon mode)
> 
> So this is what I got:
> 
> (gdb) run
> Starting program: /log/common/software/argus-3.0.7.4/sbin/argus-debug
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [New Thread 0x7ffff78f5700 (LWP 9903)]
>  ArgusWarning: 01 Aug 13 09:41:16.322918 started
> [New Thread 0x7ffff6a62700 (LWP 9904)]
>  ArgusWarning: 01 Aug 13 09:41:16.353413 ArgusGetInterfaceStatus: interface
> em2 is up
>     ArgusInfo: 01 Aug 13 09:41:16.956646 connect from argcentralm.nac.uci.edu
> *** glibc detected *** argus-debug: malloc(): memory corruption:
> 0x00007ffff34ff890 ***
> *** glibc detected *** argus-debug: malloc(): memory corruption:
> 0x00007ffff34ff890 ***
> 
> The process didn't abort/crash/etc, so I can't tell you where it failed.  What
> would you like me to try next?
> 
> 
> -- 
> Mike Iglesias                          Email:       iglesias at uci.edu
> University of California, Irvine       phone:       949-824-6926
> Office of Information Technology       FAX:         949-824-2270
> 
>