[Snort-users] FW: memory corruption in 2.8.6

Safwat Fahmy safwat.fahmy at ...14822...
Thu Apr 29 13:50:51 EDT 2010


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 at ...9988...] 
Sent: Thursday, April 29, 2010 11:55 AM
To: Safwat Fahmy; 'Russ Combs'
Cc: Snort-users at 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snort.org/pipermail/snort-users/attachments/20100429/cd7e7444/attachment.html>


More information about the Snort-users mailing list