[Ntop] FBSD crash: how can I help?
Burton at ntopSupport.com
Mon Jun 12 23:04:15 CEST 2006
Doubt it ... it's the result, not the cause. You'd just nail something
else. See static data like that is initialized once in a static data
segment. Somehow we are going outside of the bounds and trashing it. Just
changing things like that wouldn't fix the problem - it might become more
obvious or less obvious.
Using one of the --with-memorydebug= options to ./configure (./autoGen.sh)
might be a better way to go, but I don't know which of the options will work
From: ntop-bounces at unipi.it [mailto:ntop-bounces at unipi.it] On Behalf Of
Sent: Monday, June 12, 2006 2:45 PM
To: ntop at unipi.it
Subject: Re: [Ntop] FBSD crash: how can I help?
Burton Strauss wrote:
So the data segment (li values) are still being corrupted. What we need to
do is put a breakpoint on that data. Unfortunately if you move it out of
the function so that it's static and could be breakpointed, it wouldn't be
the same code... I'm not sure what to do.
we could remove gator and see what happens.. or put mutex around it
(assuming multi-threaded corruption?)
Michael Scheidell, CTO
SECNAP Network Security / www.secnap.com
scheidell at secnap.net / 1+561-999-5000, x 1131
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ntop