[ python-Bugs-1558072 ] 'setup.py install' crashes when installing python-bibtex
SourceForge.net
noreply at sourceforge.net
Thu Sep 14 05:39:05 CEST 2006
Bugs item #1558072, was opened at 2006-09-13 10:35
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1558072&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
>Group: 3rd Party
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Matejcik (spektrum)
Assigned to: Nobody/Anonymous (nobody)
Summary: 'setup.py install' crashes when installing python-bibtex
Initial Comment:
when installing python-bibtex
(http://sourceforge.net/project/showfiles.php?group_id=4825&package_id=93590&release_id=361584)
, python crashes as follows:
titan:/tmp/python-bibtex-1.2.2# python setup.py install
running install
running check
running build
running build_ext
*** glibc detected *** python: munmap_chunk(): invalid
pointer: 0xb7c530b0 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7d379e2]
/tmp/python-bibtex-1.2.2/build/lib.linux-i686-2.5/_bibtex.so[0xb7839f15]
/usr/lib/libpython2.5.so.1.0[0xb7e737ea]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalCodeEx+0x473)[0xb7ecf393]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x528e)[0xb7ecdd0e]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalCodeEx+0x7c4)[0xb7ecf6e4]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x528e)[0xb7ecdd0e]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x55bb)[0xb7ece03b]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalCodeEx+0x7c4)[0xb7ecf6e4]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalFrameEx+0x528e)[0xb7ecdd0e]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalCodeEx+0x7c4)[0xb7ecf6e4]
/usr/lib/libpython2.5.so.1.0(PyEval_EvalCode+0x63)[0xb7ecf763]
/usr/lib/libpython2.5.so.1.0[0xb7ee7ad6]
/usr/lib/libpython2.5.so.1.0(PyRun_FileExFlags+0x8e)[0xb7ee7b8e]
/usr/lib/libpython2.5.so.1.0(PyRun_SimpleFileExFlags+0x198)[0xb7ee9218]
/usr/lib/libpython2.5.so.1.0(PyRun_AnyFileExFlags+0x7a)[0xb7ee997a]
/usr/lib/libpython2.5.so.1.0(Py_Main+0xa23)[0xb7ef2e13]
python(main+0x32)[0x80485f2]
/lib/libc.so.6(__libc_start_main+0xdc)[0xb7ce987c]
python[0x8048531]
======= Memory map: ========
Neúspěšně ukončen (SIGABRT)
(This is after 'python setup.py build' successfully
finished)
Machine is i386, python is compiled with -D_FORTIFY_SOURCE
----------------------------------------------------------------------
>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-09-13 20:39
Message:
Logged In: YES
user_id=33168
I notice the second to last stack frame is in _bibtex.so.
Please file a bug report with python-bibtex.
If you can verify the problem doesn't occur with any third
party C extensions, please create a bug with a minimal test
case. This should be much easier for a python-bibtex
developer to debug than a Python developer. It's typically
also the case that these sorts of problems are in third
party extensions.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1558072&group_id=5470
More information about the Python-bugs-list
mailing list