[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-bugs
Subject:    bin/87729: most calls to malloc(3) generate warnings in valgrind
From:       Bradley T Hughes <bhughes () trolltech ! com>
Date:       2005-10-20 15:19:57
Message-ID: 200510201519.j9KFJvd5050379 () www ! freebsd ! org
[Download RAW message or body]


> 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:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"


[prev in list] [next in list] [prev in thread] [next in thread]