From owner-freebsd-hackers Wed Jun 10 13:02:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29418 for freebsd-hackers-outgoing; Wed, 10 Jun 1998 13:02:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29222 for ; Wed, 10 Jun 1998 13:01:46 -0700 (PDT) (envelope-from wjw@surf.IAEhv.nl) Received: from surf.IAEhv.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id WAA00350 for ; Wed, 10 Jun 1998 22:01:42 +0200 (CEST) Received: (from wjw@localhost) by surf.IAEhv.nl (8.8.7/8.8.7) id WAA03724 for hackers@freeBSD.org; Wed, 10 Jun 1998 22:01:42 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199806102001.WAA03724@surf.IAEhv.nl> Subject: debugging memory allocation in -stable To: hackers@FreeBSD.ORG Date: Wed, 10 Jun 1998 22:01:41 +0200 (MET DST) Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Working on some stuff with variant links, crashed became my life. But I have some code partially working. Only a few symbolic links later, I get a crash due to having already free'ed some buffer. I'm pretty shure I have to release this buffer in my code, but know I'd like to know where this buffer was malloced in the first place. How do I figure this out? Once I enhanced a malloc package with tracing and tracking, and I must say that vmstat -m does reveil losts of nice info. But one feature I now mis: the string holding the filename/number where the allocation took place. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message