Everybody, thanks all for the information! For what it's worth, I'm now running kannel (cvs update from yesterday) compiled with:
./configure --prefix=/usr --with-defaults=speed --disable-docs --disable-ssl --enable-debug (malloc checking off) I'll be watching it closely to see what happens. As for memory leaks, can't we use something like electricfence? On another issue, smsbox got hit hard with a number of requests and this happened: 2002-02-01 07:00:01 [3] PANIC: gwlib/thread.c:100: mutex_unlock_real: Mutex failure! (Called from gwlib/conn.c:156:unlock_out_real.) Ideas? On Friday, 2002-02-01 at 03:39:20 AM, Stipe Tolj scribbled: > Richard Braakman wrote: > > > > In either case, Stipe is right in that the panic was from the malloc > > checking code, and not from the server running out of memory. > > I just wanted to point out that if you get that panic, it still > > means there's an actual bug. You can hide it by turning off the > > malloc checker and installing lots of memory :-) > > Richard, can we utilize some function to detect memory leaks using the > checking malloc routines already built-in Kannel? > > Stipe -- Benjamin Lee 71-75 City Rd, South Melbourne, VIC 3006 Australia http://www.dotwap.com/ Phone +61 3 9698 1840 Mobile +61 414 717 573 Fax +61 3 9698 1841
