Re: BUG #1897: dmalloc memory error on PQconnectdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Wade Hampton" <wade(dot)hampton(at)nsc1(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1897: dmalloc memory error on PQconnectdb
Date: 2005-09-20 15:41:06
Message-ID: 6734.1127230866@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Wade Hampton" <wade(dot)hampton(at)nsc1(dot)net> writes:
> I have a multithreaded application using Postgresql and am testing for
> memory leaks. I compiled and linked with dmallocth. My PGconnect() is now
> causing a dmalloc abort. The error appears to be a calloc of 0 elements of
> 40 bytes in libkrb5, called from libpq.

(1) Why is that a bug? calloc of 0 elements is explicitly allowed by
the Single Unix Spec:
http://www.opengroup.org/onlinepubs/007908799/xsh/calloc.html

(2) If you do think it's a bug, why are you complaining to us rather
than to the Kerberos people?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2005-09-20 16:13:17 Re: BUG #1898: Problema En Tipo de dato Real.
Previous Message Ing. Jhon Carrillo - Caracas, Venezuela 2005-09-20 13:11:42 problem start database