From owner-cvs-all Tue Apr 23 21:59:18 2002 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 5846537B41A; Tue, 23 Apr 2002 21:58:56 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g3O4waHx096287; Wed, 24 Apr 2002 06:58:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Brian Dean Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Memory overwrite problem in the -current kernel ?? In-Reply-To: Your message of "Tue, 23 Apr 2002 22:44:21 EDT." <20020423224421.B69940@neutrino.bsdhome.com> Date: Wed, 24 Apr 2002 06:58:36 +0200 Message-ID: <96286.1019624316@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020423224421.B69940@neutrino.bsdhome.com>, Brian Dean writes: >On Tue, Apr 23, 2002 at 01:54:17PM +0200, Poul-Henning Kamp wrote: >> This commit detects a memory overwrite problem in the kernel which >> happens before we ever get into userland for the first time. > >Do you know the address being corrupted? If so, try breaking into ddb >early on and set a hardware watchpoint. It was a modified pointer being returned to free(9), it's solved now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message