[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2013-01-07 Thread Stefan Krah 

Stefan Krah added the comment:

Closing as a duplicate of #10156, which has several patches.

--
resolution:  - duplicate
stage: needs patch - committed/rejected
status: open - closed
superseder:  - Initialization of globals in unicodeobject.c

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2013-01-05 Thread Franck Michea 

Changes by Franck Michea franck.mic...@gmail.com:


--
nosy: +kushou

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

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/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-11-18 Thread Antoine Pitrou 

Antoine Pitrou added the comment:

Does this need to be a release blocker? I don't know what the concrete point of 
--without-doc-strings is.

--
nosy: +pitrou

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-11-18 Thread Stefan Krah 

Stefan Krah added the comment:

The deeper issue is that globals in unicodeobject.c are used before
they are initialized. So I thought that should be cleared up before
the next release.

Basically, strings are used as keys during type initializations
*before* _PyUnicode_Init() is called.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-11-18 Thread Georg Brandl 

Changes by Georg Brandl ge...@python.org:


--
priority: release blocker - critical

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-10-05 Thread Gregory Andersen 

New submission from Gregory Andersen:

Seems unicode_empty is still NULL at this point.

A gdb backtrace from an x86_64 build.  Reproduced on i686 and mips build as 
well.

Program received signal SIGSEGV, Segmentation fault.
0x0044f61e in PyUnicode_DecodeUTF8Stateful (s=0x59a767 , size=0, 
errors=0x0, consumed=0x0) at Objects/unicodeobject.c:4726
4726Py_INCREF(unicode_empty);
(gdb) bt
#0  0x0044f61e in PyUnicode_DecodeUTF8Stateful (s=0x59a767 , size=0, 
errors=0x0, consumed=0x0) at Objects/unicodeobject.c:4726
#1  0x00433087 in PyType_Ready (type=0x7d5340) at 
Objects/typeobject.c:4235
#2  0x004332ae in PyType_Ready (type=optimized out) at 
Objects/typeobject.c:4116
#3  PyType_Ready (type=0x7d54e0) at Objects/typeobject.c:4146
#4  0x0041bbfe in _Py_ReadyTypes () at Objects/object.c:1576
#5  0x004a6eb0 in _Py_InitializeEx_Private (install_sigs=optimized 
out, install_importlib=optimized out) at Python/pythonrun.c:301
#6  Py_InitializeEx (install_sigs=optimized out) at Python/pythonrun.c:401
#7  Py_Initialize () at Python/pythonrun.c:407
#8  0x004bb9fc in Py_Main (argc=1, argv=0x82f010) at Modules/main.c:646
#9  0x0041949e in main (argc=1, argv=0x7fffe658) at 
./Modules/python.c:66

--
components: Interpreter Core
messages: 172097
nosy: Gregory.Andersen
priority: normal
severity: normal
status: open
title: Building with configure option --without-doc-strings crashes first 
time through PyUnicode_DecodeUTF8Stateful
type: crash
versions: Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-10-05 Thread Stefan Krah 

Stefan Krah added the comment:

This seems related to #9242: _Py_InitializeEx_Private() calls _Py_ReadyTypes(),
which uses the Unicode API, well before actually calling _PyUnicode_Init().

--
nosy: +georg.brandl, skrah
priority: normal - release blocker
stage:  - needs patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16143] Building with configure option --without-doc-strings crashes first time through PyUnicode_DecodeUTF8Stateful

2012-10-05 Thread Stefan Krah 

Stefan Krah added the comment:

Sorry, wrong issue number: Related to #10156.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16143
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com