bin/87729: most calls to malloc(3) generate warnings in valgrind

Bradley T Hughes bhughes at trolltech.com
Thu Oct 20 08:20:24 PDT 2005


>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 at 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:


More information about the freebsd-bugs mailing list