From owner-freebsd-hackers Wed Mar 27 14:23:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id 050B737B416; Wed, 27 Mar 2002 14:23:17 -0800 (PST) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g2RMNBx43361; Wed, 27 Mar 2002 17:23:12 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 27 Mar 2002 17:23:11 -0500 (EST) From: Jeff Roberson To: Alfred Perlstein Cc: Terry Lambert , , Subject: Re: uma and double free detection? In-Reply-To: <20020327213247.GO93885@elvis.mu.org> Message-ID: <20020327172135.I16840-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 27 Mar 2002, Alfred Perlstein wrote: > * Terry Lambert [020327 13:30] wrote: > > Alfred Perlstein wrote: > > > > > > Can uma diagnose double free's? It doesn't seem to be able to > > > under a GENERIC config. :( > > > > THat's an INVARIANTS thing, even without UMA... > > /usr/src/sys/i386/conf % grep INVA BRIGHT > options INVARIANTS #Enable calls of extra sanity checking > options INVARIANT_SUPPORT #Extra sanity checks of internal structu > > All I got was a panic because uma seemed to get confused rather than > catch the double free. > Yikes, a panic? From a double free? Was this from malloc or zalloc? Are you sure there was no other memory corruption? Thanks, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message