Re: 800RC1 valgrind-detected bug ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: strk <strk(at)keybit(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 800RC1 valgrind-detected bug ?
Date: 2004-12-14 14:11:41
Message-ID: 14037.1103033501@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

strk <strk(at)keybit(dot)net> writes:
> ==15489== Syscall param write(buf) contains uninitialised or unaddressable byte(s)

Valgrind is fairly useless for debugging postgres, because it doesn't
know the difference between alignment-pad bytes in a struct and real
data. What you've got here is a gripe arising from writing out a
struct containing padding.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-12-14 14:23:27 Re: bgwriter changes
Previous Message Bruce Momjian 2004-12-14 13:54:40 Re: bgwriter changes