Re: [HACKERS] 800RC1 valgrind-detected bug ?

[Oliver Jowett]

Tom Lane wrote:
strk <[EMAIL PROTECTED]> 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.
Is there any risk of leaking sensitive data to a file or the network via 
those uninitialized alignment padding bytes?

-O
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] 800RC1 valgrind-detected bug ?

[Tom Lane]

strk <[EMAIL PROTECTED]> 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

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster