Re: leak in libpq, getpwuid

On Wed, Feb 18, 2009 at 5:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <gryzman(at)gmail(dot)com> writes:
>> same thing on debian, well - almost:
>
>> ==8261== at 0x4023D6E: malloc (vg_replace_malloc.c:207)
>> ==8261== by 0x43B1930: (within /lib/i686/cmov/libc-2.7.so)
>> ==8261== by 0x43B222B: __nss_database_lookup (in /lib/i686/cmov/libc-2.7.so)
>> ==8261== by 0x6C98F5B: ???
>> ==8261== by 0x6C9B0B4: ???
>> ==8261== by 0x4358ED1: getpwuid_r (in /lib/i686/cmov/libc-2.7.so)
>> ==8261== by 0x417ED3D: (within /usr/lib/libpq.so.5.1)
>> ==8261== by 0x416A7A8: (within /usr/lib/libpq.so.5.1)
>> ==8261== by 0x416E5CA: (within /usr/lib/libpq.so.5.1)
>> ==8261== by 0x416E709: (within /usr/lib/libpq.so.5.1)
>> ==8261== by 0x416EA4E: PQconnectStart (in /usr/lib/libpq.so.5.1)
>> ==8261== by 0x416EAA1: PQconnectdb (in /usr/lib/libpq.so.5.1)
>
> [ shrug... ] You're bugging the wrong people about this. A leak
> inside getpwuid_r is a glibc bug, not our bug.
>

thought so, but it is good to check on both sides of fence.
thanks

--
GJ