Skip site navigation (1) Skip section navigation (2)

Core dump on HP

From: Michael Brusser <michael(at)synchronicity(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Core dump on HP
Date: 2003-06-26 18:37:24
Message-ID: DEEIJKLFNJGBEMBLBAHCAEBBDFAA.michael@synchronicity.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi, folks;
We're running Postgres 7.3.2. 
At the end of some procedure we get a core dump on HP-11.
This does not seem reproducible on Solaris or Linux.
Working with debugger we get this stack:

#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
(gdb) where
#0 0xc0185a20 in mallinfo+0x2144 () from /usr/lib/libc.2
#1 0xc01821c0 in __thread_callback_np+0x894 () from /usr/lib/libc.2
#2 0xc0187fa4 in realloc+0x1c4 () from /usr/lib/libc.2
#3 0xc018f420 in putenv+0xe8 () from /usr/lib/libc.2

It looks that problem occurs when we releasing TCL interpreter, also 
the problem can be avoided if in pgtcl.c this code is commented out:

  if (tclversion >= 8.1)
      putenv("PGCLIENTENCODING=UNICODE");

I found another report on putenv problem:
http://archives.postgresql.org/pgsql-bugs/1999-11/msg00007.php

Are we're dealing with essentially same root cause?
Is there a recommended solution?

Thank you,
Michael.



pgsql-hackers by date

Next:From: Mikhail TerekhovDate: 2003-06-26 18:39:45
Subject: Re: PlPython
Previous:From: DeJuan JacksonDate: 2003-06-26 18:31:46
Subject: Re: PlPython

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group