From owner-freebsd-current Tue Aug 18 09:06:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09526 for freebsd-current-outgoing; Tue, 18 Aug 1998 09:06:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-35.ix.netcom.com [207.93.136.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09521 for ; Tue, 18 Aug 1998 09:06:36 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id JAA14177; Tue, 18 Aug 1998 09:05:56 -0700 (PDT) (envelope-from tomdean) Date: Tue, 18 Aug 1998 09:05:56 -0700 (PDT) Message-Id: <199808181605.JAA14177@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: <199808172233.WAA12072@dingo.cdrom.com> (message from Mike Smith on Mon, 17 Aug 1998 22:33:53 +0000) Subject: Re: Calloc or VM Problem <== My Problem, Now Solved Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp showed me how to find this kind of problem. setenv MALLOC_OPTIONS UJA ktrace -t u ./your-program It was my problem. The initial structure was somewhat small. In all the transactions, a few dozen bytes were calloc'ed for a small table. After receiving his message, the problem was easy to find. In pouring over the entire structure, the remainder was calloc'ed for a future table and never used, thus not corrupted. Thanks for your help, tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message