Nope... gdbm is sloppy WRT to allocations - which also means it's sensitive to corruption in the allocation chains. I suppose you could try running under valgrind (although there is a big performance penalty). That MIGHT find something...
(But I've never even tried ntop under valgrind in a FreeBSD environment - so there will probably be a big set of 'standard' exclusions to work through first) -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Buraglio Sent: Wednesday, January 19, 2005 10:40 AM To: [email protected] Subject: Re: [Ntop] flow collector segfault Any ideas of what I can look at next? nb On Jan 17, 2005, at 7:54 PM, Nick Buraglio wrote: > From the gnu mirrors, it looks like 1.8.3 is the newest version of > gdbm (which I'm sure you already knew) > > nb > <snip /> _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
