Snort mailing list archives
Re: FW: memory corruption in 2.8.6
From: "Billy Marshall" <Billy.Marshall () state co us>
Date: Thu, 29 Apr 2010 09:54:44 -0600
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
Current thread:
- Re: memory corruption in 2.8.6, (continued)
- Re: memory corruption in 2.8.6 Russ Combs (Apr 28)
- Re: memory corruption in 2.8.6 Safwat Fahmy (Apr 28)
- Re: memory corruption in 2.8.6 Russ Combs (Apr 28)
- Re: memory corruption in 2.8.6 Joel Esler (Apr 28)
- Re: memory corruption in 2.8.6 Safwat Fahmy (Apr 28)
- Re: FW: memory corruption in 2.8.6 Russ Combs (Apr 28)
- Re: FW: memory corruption in 2.8.6 Safwat Fahmy (Apr 28)
- Re: FW: memory corruption in 2.8.6 Russ Combs (Apr 29)
- Re: FW: memory corruption in 2.8.6 Safwat Fahmy (Apr 29)
- Re: FW: memory corruption in 2.8.6 Billy Marshall (Apr 29)
- Re: FW: memory corruption in 2.8.6 Safwat Fahmy (Apr 29)