Sorry, I wasn't very clear. With the original code, the call itself
reports success (return code 0), but I can't verify it as attempting
access the parameters causes an exception [eg print str(snapshot_id)
raises "WindowsError: exception: stackoverflow" in _StringFromCLSID]. If
I catch the exception and try to continue, I get other WindowsError
exceptions, typically from attempting to access bad memory addresses.
Peter
[EMAIL PROTECTED] schrieb:
> The following workaround works with 64-bit (and I assume 32-bit)
pythons:
> ...
>
> The following (original code) only works with 32-bit python (and seems
to
> cause a memory stomp with 64-bit python) [here guid_null is passed by
> value]:
> ...
I understand what you mean, except I do NOT understand what 'cause a
memory stomp' mean.
Does the code change the passed in guid_null, which you didn't expect, or
what?
Thanks,
Thomas
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users
