> Without further information, I cannot consider this as a problem in
> Python.
> I know other extension modules that manage memory in their own way, and
> work.
> It's more probably an issue in the code of your type.
>
> --
> Amaury Forgeot d'Arc
Ok, thank you, but I'm still hoping, someone cou
> This said, there may be a bug somewhere, but what do you want us to look
> at?
> Do you have a case that we could reproduce and investigate?
>
> --
> Amaury Forgeot d'Arc
Thank you, I'm not a C-Developer,
but still I have one more detail:
I call py_decRef( pyObj) of dll (version 3.1.1),
( w
Sorry, I wrote tp_alloc in last post, it should be always tp_dealloc:
My tp_dealloc method (of non-subtypable type) calls the freeMem-method
of a memory manager (this manager was also used for the corresponding
allocation).
This freeMem-method deallocates and modifies the memory,
which is a val
My tp_dealloc method (of non-subtypable type) calls the freeMem-method
of a memory manager (this manager was also used for the corresponding
allocation).
This freeMem-method deallocates and modifies the memory,
which is a valid action, because after free, the memory-manager
has ownership of th
Hi,
when embedding python 3.1, I have my own free-method in tp_dealloc.
The allocated memory is in host-memory, not in python (dll). Now, the problem
is, Python appears to read-access the deallocated memory still after
tp_dealloc. After tp_dealloc, I get an access violation if the pyobject-header
