From: g.hintermayer@inode.at
To: pgsql-interfaces@postgresql.org
Subject: Re: still memory leaks with libpgtcl
Date: 8 Jan 2003 06:30:58 -0800
Message-ID: <bd4db85f.0301080630.5f2cdc0a@posting.google.com> (raw)
References: <785.1041999818@sss.pgh.pa.us>
<bd4db85f.0301080219.3763ad56@posting.google.com>
The Tcl_Channel type mismatch was wrong alarm, ths is detected
automatically (but should be corrected in future versions anyhow).
The SEGV is, when Tcl_DontCallWhenDeleted is called, when the channel
is shut down (PgDelConnectionId). Unfortunately notifies->interp is
NULL and Tcl_DontCallWhenDeleted does not like that at all.
This might be the reason, why the patch from ljb (sorry, no name)
helps.
I will track down that deeper tomorrow when I'm at home, posting via
Google takes too long.
Gerhard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: g.hintermayer@inode.at
Subject: Re: still memory leaks with libpgtcl
In-Reply-To: <bd4db85f.0301080630.5f2cdc0a@posting.google.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox