[Snort-users] Memory leaks

roman at ...438... roman at ...438...
Thu May 17 09:37:28 EDT 2001

Snort does indeed support debugging memory libraries such
as efence.  However in this case, efence won't help us since
this library only does fence-posting; checking for code which
overruns the boundary of a malloc, or code which attempts
to use memory which has been free-d (note: I definitely swear
by efence; it is so useful!).  As far as I can tell, the
central issue we are encountering is memory which is not
de-allocated.  Those, memleak checking libraries are not always
a panecea.  I've tried dmalloc with the Snort code, and it
would flag me on code which calloc()s, but does not free the
associated memory in the _same_ function.

Anyone have experience with any checker which might be
better? or perhaps a guru who can tweak dmalloc?


> I noticed that there are many problems related to memory leaks -- does snort
> already support ElectricFence or other free memleak checkers during build?
> -- 
> ralf.hildebrandt at ...821...                            innominate AG
> System Engineer                        Don't be afraid of what you see -
> Diplom-Informatiker                     be afraid of what you don't see!
> tel: +49.(0)7000.POSTFIX  fax: +49.(0)30.308806-698         
> _______________________________________________
> Snort-users mailing list
> Snort-users at lists.sourceforge.net
> Go to this URL to change user options or unsubscribe:
> http://lists.sourceforge.net/lists/listinfo/snort-users
> Snort-users list archive:
> http://www.geocrawler.com/redir-sf.php3?list=snort-users

This message was sent using Voicenet WebMail.

More information about the Snort-users mailing list