Hi,
I've found something strange while using unicode objects in embedded python.
Here is a situation. I'm creating a couple of unicode objects and then some
exception is thrown. While handling exception I create 2 unicode object. The 1.
one is created sucessfully but the second one not. The problem is in
_PyUnicode_New()
on line (1):
if (free_list) {
unicode = free_list; /*<- (1)*/
free_list = *(PyUnicodeObject **)unicode;
In statement "unicode = free_list;" "unicode" pointer is bad pointer, in fact
it's address is 5 bytes "lower" (i.e. should be 0x030bc3ff but is 0x030bc3fa).
It looks like this only happens when exception is thrown. Anyone know where
could be the problem? I'm using python 3.2.1 on Vista with MSVS 2010
Trigve
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4