From owner-freebsd-hackers Fri Oct 30 14:16:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02192 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 14:16:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com ([207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02185 for ; Fri, 30 Oct 1998 14:16:33 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id OAA13544 for ; Fri, 30 Oct 1998 14:16:30 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id OAA01317 for hackers@freebsd.org; Fri, 30 Oct 1998 14:16:24 -0800 (PST) Message-ID: <19981030141624.A1244@thought.org> Date: Fri, 30 Oct 1998 14:16:24 -0800 From: Gary Kline To: Hackers Mailing List Subject: Memory leak location tool? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm double-checking because the word that I've heard thus far is `No, not really.' But I thought I'd check this worldwide list to confirm:: Are there any free tools to detect likely memory leaks? Tools like Purify aren't quite what I'm looking for. Anybody? gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message