Mailinglist Archive: zypp-devel (149 mails)
| < Previous | Next > |
[zypp-devel] Re: libzypp-bindings (python) memory leak of type 'zypp::ResPool *'
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Wed, 3 Sep 2008 21:56:44 +0200
- Message-id: <20080903195644.GA334@xxxxxxxxxxxxx>
* Jan-Simon Möller <dl9pf@xxxxxx> [Sep 03. 2008 20:44]:
Yeah, libzypp does not provide a destructor since there's no reason
for it. If the ResPool is gone, libzypp is gone ;-)
Swig can probably be fooled by defining an empty ResPool destructor.
The query interface (to satsolver) has undergone quite some changes. I
just got an initial swig binding for satsolver working.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Hi Klaus, hi list !
swig/python detected a memory leak of type 'zypp::ResPool *', no destructormypool = zy.pool()
found.
Yeah, libzypp does not provide a destructor since there's no reason
for it. If the ResPool is gone, libzypp is gone ;-)
Swig can probably be fooled by defining an empty ResPool destructor.
I got it working but next stop is to query the pool, which fails.
The query interface (to satsolver) has undergone quite some changes. I
just got an initial swig binding for satsolver working.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |