[issue9242] unicodeobject.c: use of uninitialized values

2013-01-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I forgot mention the issue number in commit messages. See changeset3570e04f4ea9 and changesetbf347198fbaf. Is the issue fixed now? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242

[issue9242] unicodeobject.c: use of uninitialized values

2013-01-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: changeset 3570e04f4ea9 and changeset bf347198fbaf -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242 ___

[issue9242] unicodeobject.c: use of uninitialized values

2013-01-08 Thread Stefan Krah
Stefan Krah added the comment: The utf_32_le_decode invalid access is gone; for Valgrind the issue is fixed (I didn't look at the patch, no time ATM, sorry). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242

[issue9242] unicodeobject.c: use of uninitialized values

2013-01-08 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242 ___

[issue9242] unicodeobject.c: use of uninitialized values

2013-01-06 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: 3.2 is affected too. The PEP-393 changes fixes this bug in 3.3+. Here is a simple patch. -- assignee: - serhiy.storchaka keywords: +patch nosy: +serhiy.storchaka stage: - patch review versions: +Python 3.2 Added file:

[issue9242] unicodeobject.c: use of uninitialized values

2013-01-04 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242 ___

[issue9242] unicodeobject.c: use of uninitialized values

2011-07-07 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9242 ___ ___

[issue9242] unicodeobject.c: use of uninitialized values

2010-07-16 Thread Stefan Krah
Stefan Krah stefan-use...@bytereef.org added the comment: Here is a minimal example how to reproduce this issue, extracted from UTF32LETest. valgrind --db-attach=yes --suppressions=Misc/valgrind-python.supp ./python uninitialized.py It seems that in Lib/codecs.py the equivalent of

[issue9242] unicodeobject.c: use of uninitialized values

2010-07-13 Thread Stefan Krah
New submission from Stefan Krah stefan-use...@bytereef.org: Not sure if this is valid or if there is some internal trickery that Valgrind isn't aware of. If it's the latter, perhaps an entry to Misc/valgrind.supp could be added. test_bug1175396 (__main__.UTF32Test) ... ==26861== Conditional

[issue9242] unicodeobject.c: use of uninitialized values

2010-07-13 Thread Marc-Andre Lemburg
Marc-Andre Lemburg m...@egenix.com added the comment: Stefan Krah wrote: New submission from Stefan Krah stefan-use...@bytereef.org: Not sure if this is valid or if there is some internal trickery that Valgrind isn't aware of. If it's the latter, perhaps an entry to Misc/valgrind.supp

[issue9242] unicodeobject.c: use of uninitialized values

2010-07-13 Thread Stefan Krah
Stefan Krah stefan-use...@bytereef.org added the comment: const int iorder[4] = {0, 1, 2, 3}; const isn't possible, iorder is modified later on. Adding the array dimension did not change anything. Making everything const (see below) did not change anything either. I presume that Valgrind