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

Re: "double free" segfault back in pyscopg2 2.5

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: psycopg(at)postgresql(dot)org
Subject: Re: "double free" segfault back in pyscopg2 2.5
Date: 2013-06-20 15:42:21
Message-ID: 1371742941.3159.10.camel@risotto.smithersbet.com (view raw or flat)
Thread:
Lists: psycopg
On Thu, 2013-06-20 at 19:34 +0530, Gangadharan S.A. wrote:

> The fix would be to call conn_close after untracking the object in
> connection_type.c:connection_dealloc().

Pushed correction at
https://github.com/dvarrazzo/psycopg/commit/889b1d826e9cf0ecbc9af938bad72937592af5e4

Is this enough to consider the issue fixed?

I've checked other destructors and we untrack the object before any
other operation in all the objects.

Thanks


-- 
Daniele



In response to

Responses

psycopg by date

Next:From: Gangadharan S.A.Date: 2013-06-20 15:47:02
Subject: Re: "double free" segfault back in pyscopg2 2.5
Previous:From: Daniele VarrazzoDate: 2013-06-20 15:22:20
Subject: Re: "double free" segfault back in pyscopg2 2.5

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