Date: Thu, 20 Oct 2005 15:19:57 GMT From: Bradley T Hughes <bhughes@trolltech.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/87729: most calls to malloc(3) generate warnings in valgrind Message-ID: <200510201519.j9KFJvd5050379@www.freebsd.org> Resent-Message-ID: <200510201520.j9KFKJJ9029085@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 87729
>Category: bin
>Synopsis: most calls to malloc(3) generate warnings in valgrind
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Oct 20 15:20:18 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Bradley T Hughes
>Release: 6.0-RC1
>Organization:
Trolltech AS
>Environment:
FreeBSD reticent.troll.no 6.0-RC1 FreeBSD 6.0-RC1 #28: Mon Oct 17 08:46:08 CEST 2005 root@reticent.troll.no:/usr/obj/usr/src/sys/RETICENT i386
>Description:
When using valgrind from ports to debug a program, most calls to malloc(3) generate a warning about a comparison depending on uninitialized values.
>How-To-Repeat:
Run valgrind on /bin/ls
>Fix:
Apply the attached patch to src/lib/libc/stdlib/malloc.c, it makes sure that all bits in the pginfo.bits bitfield are initialized.
>Release-Note:
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510201519.j9KFJvd5050379>