On 12/1/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Andy,
I think that the Python service wrapper sometimes returns data on the
stack, the data allocated by PyValue appears to be valid inside the
wrapper itself but gets out of scope after the wrapper has returned,
causing memory violations or garbage to be returned.
Could you please take a look at my change under revision r481279? I
copied a char* into a new string to workaround the particular case I ran
into, but there's probably a better way to fix this and make sure that
strings returned by the wrapper in general are allocated on the heap
instead of the stack.
Thanks...
--
Jean-Sebastien
Hi Sebastien,
This change looks good, thanks.
It strikes me that we may need some kind of "extension-builder's
library" that can be used to manage data and the conversion of data
and other chunks of code that we are seeing repeated in various places
in the extensions. With something like this, issues such as the one
you found above should be found & fixed earlier. What do people think?
Cheers
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
