From owner-freebsd-hackers Mon Sep 22 02:24:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA28501 for hackers-outgoing; Mon, 22 Sep 1997 02:24:26 -0700 (PDT) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA28493 for ; Mon, 22 Sep 1997 02:24:19 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id LAA00951 for ; Mon, 22 Sep 1997 11:15:28 +0200 (SAT) Received: by citadel via recvmail id 949; Mon Sep 22 11:15:26 1997 by gram.cdsec.com (8.8.5/8.8.5) id KAA07518 for hackers@freebsd.org; Mon, 22 Sep 1997 10:56:11 +0200 (SAT) From: Graham Wheeler Message-Id: <199709220856.KAA07518@cdsec.com> Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) To: hackers@freebsd.org Date: Mon, 22 Sep 1997 10:56:10 +0200 (SAT) In-Reply-To: <199709220555.WAA15014@usr07.primenet.com> from "Terry Lambert" at Sep 22, 97 05:55:09 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just an update on the original problem I had - on Friday we restarted the gateway process, this time linked with the non-debug version of the libmalloc library (the version linked with the debug version had been running for about 30 hours with no problems). As of this (Monday) morning, the process is still running happily. I will still try get the client to run a version linked against the GNU malloc library sometime this week, and see how that goes. And I will also try the efence approach, although the libmalloc_d should have caught overruns if there are any (and I'm pretty sure there aren't, having checked every new/delete/memcpy/memset/strcpy/strcat and looping pointer iteration with a fine tooth comb by now, and having added about 100 more asserts to the code). So maybe there is a bug in pkhmalloc after all...(sorry Poul). For those who missed the start of this thread, when linked with pkhmalloc, the gateway process was running for at most thirty minutes at a time before ending in an infinite loop in the malloc code. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/