well at first I could not believe what I was seeing ...
Look at the following code (ecpg/lib/execute.c):
const char *locale=setlocale(LC_NUMERIC, NULL);
Well at least on glibc-2.2 it seems that setlocale retuns a pointer to
malloced memory, and frees this pointer on subsequent calls to
setlocale. This is standard conformant and has good reasons. But used as
above it is lethal (but not lethal enough to be easily recognized). So
the content locale points to is freed by the second call to setlocale.
The remedy is easy (given that _no other_ call to setlocale happens
const char *locale=setlocale(LC_NUMERIC, "C");
So I would kindly ask you to take a second look at every invokation of
setlocale. And to apply the following patch.
pgsql-hackers by date
|Next:||From: Dave Page||Date: 2001-09-24 07:37:20|
|Subject: Re: [ODBC] UTF-8 support|
|Previous:||From: Tatsuo Ishii||Date: 2001-09-24 07:12:59|
|Subject: Re: UTF-8 support|
pgsql-patches by date
|Next:||From: Justin Clift||Date: 2001-09-24 15:02:52|
|Subject: Re: Makefiles for building with mingw32 on win32|
|Previous:||From: Gerhard Häring||Date: 2001-09-24 04:31:55|
|Subject: Re: [PATCHES] Makefiles for building with mingw32 on win32|