Re: [Orbit-python-list] Any activity?

[Christian R. R. <ki...@as...>]

On Fri, 25 Jan 2002, Roland Mas wrote:

> Roland Mas (2002-01-25 11:21:57 +0100) :
>
> Well, it's done.  Know that this fix shows a memory leak, though.  It
> doesn't exactly /introduce/ this leak, since the conditions leading to
> it previously led to a segfault, but there it is.  I had a fix for
> that leak, but it was a fix for ORBit, and I was told by one ORBit
> guru that it was wrong.  Apparently it's okay for applications
> (including ORBit-Python) to fiddle with the deep innards of ORBit
> proper (including ...->_private members of structs).  I'm looking for
> another, ORBit-Python-only, fix.

Have you tested with ORBit-0.5.12? At least from what I remember, we had a
lot of trouble because somebody was murdering ->_private members of
deactivated servants.

I can't see a way to fix that without having the ORBit folks reversing
that patch.

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL