From owner-freebsd-current Fri Jul 7 23:42:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4B7D837B6D2 for ; Fri, 7 Jul 2000 23:42:51 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA10922; Sat, 8 Jul 2000 08:42:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Alexander N. Kabaev" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Suspicious warnings in -CURRENT In-reply-to: Your message of "Fri, 07 Jul 2000 19:00:11 EDT." Date: Sat, 08 Jul 2000 08:42:45 +0200 Message-ID: <10920.963038565@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Alexander N. Kabaev" writes: >After today's buildworld, I am seeing lots of warning messages from libc like: > >expr in free(): warning: modified (chunk-) pointer > >Does it happen to anyone else on this list? I see it in vi(1). Somebody enable the 'A' option of phkmalloc and examine the core. ln -sf A /etc/malloc.conf -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 freebsd-current" in the body of the message