[issue11048] "import ctypes" causes segfault on read-only filesystem

2016-07-27 Thread Emanuel Barry
Changes by Emanuel Barry : -- stage: test needed -> resolved ___ Python tracker ___ ___

[issue11048] "import ctypes" causes segfault on read-only filesystem

2016-07-27 Thread STINNER Victor
STINNER Victor added the comment: Sorry, I'm unable to reproduce the crash using the read-only filesystem. But an assertion confirmed me that the restype is not initialized which is an obvious bug. ctypes-erofs-crash.diff: LGTM. By the way, the flags field is not initialized neither, but

[issue11048] "import ctypes" causes segfault on read-only filesystem

2016-07-27 Thread Roundup Robot
Roundup Robot added the comment: New changeset ab4975520c7d by Victor Stinner in branch '3.5': ctypes: fix CThunkObject_new() https://hg.python.org/cpython/rev/ab4975520c7d New changeset da9898e7e90d by Victor Stinner in branch 'default': Merge 3.5 (issue #11048)

[issue11048] "import ctypes" causes segfault on read-only filesystem

2016-07-26 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3, Python 3.4 ___ Python tracker

[issue11048] import ctypes causes segfault on read-only filesystem

2013-02-14 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- stage: - test needed versions: +Python 3.4 -Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11048 ___

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-30 Thread Marcin Bachry
Marcin Bachry hegel...@gmail.com added the comment: This patch fixes issue with unitialized variable which makes ctypes crash in error handler. Note that for you it merely turns Segmentation fault into MemoryError exception. Python ships with buggy version of libffi, which tries to allocate

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-30 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: It would be nice to add a unit test to this patch. I don't think messing with read-only filesystems is feasible in regrtest, but it seems from reading _ctypes_alloc_callback() source that similar behavior can be

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-29 Thread Pavel Labushev
Pavel Labushev p.labus...@gmail.com added the comment: How to reproduce: # mkdir /mnt/readonly # mount --bind / /mnt/readonly # mount -o remount,ro /mnt/readonly # mount -t proc proc /mnt/readonly/proc # chroot /mnt/readonly python3.2 -c import ctypes Segmentation fault If your python build

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-29 Thread Daniel Urban
Daniel Urban urban.dani...@gmail.com added the comment: Thanks for the instructions. You're right, this way I can reproduce the segfault. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11048

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-28 Thread Pavel Labushev
New submission from Pavel Labushev p.labus...@gmail.com: import ctypes causes segfault on read-only filesystem This regression was introduced in python-2.6.6 and exists in all the later versions. To reproduce run python -c import ctypes on read-only filesystem: (gdb) file python3.2 Reading

[issue11048] import ctypes causes segfault on read-only filesystem

2011-01-28 Thread Daniel Urban
Daniel Urban urban.dani...@gmail.com added the comment: I cannot reproduce this with the current py3k branch (Ubuntu 10.04 32 bit). -- nosy: +durban type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11048