Re: FW: memory corruption in 2.8.6

["Safwat Fahmy" <safwat.fahmy () safemedia com>]

Billy:

 

Thank you for your direction 

When snort inline started without the demon option and using the "&" instead
it works like a charm, and that is a good indication  and proof that all my
libc and gcc libs are in order. 

What do you think?

Thanks

Safwat

 

 

From: Billy Marshall [mailto:Billy.Marshall () state co us] 
Sent: Thursday, April 29, 2010 11:55 AM
To: Safwat Fahmy; 'Russ Combs'
Cc: Snort-users () lists sourceforge net
Subject: Re: [Snort-users] FW: memory corruption in 2.8.6

 

Hi,

 

*** glibc detected *** malloc(): memory corruption

 

Recent versions of glibc offer minimal diagnostic. Probable
causes:

 Writing beyond the end of a memory block obtained via malloc
or realloc.

 Writing/reading memory that has been released with free().

Perhaps you need to investigate your compiler with respect to a 64 bit OS
memory addressing schema.

------------------------------------------------------------------------------

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users