I'm running unittests on a CentOS 6.4 Virtual Box slave via Jenkins on a Windows host. Randomly I get core dumps for no obvious reason. I don't use any C extension in my code and don't use ctypes. The (proprietary) software is plain Python with a multi-threaded architecture. There might be a threading race condition in the code but according to http://stackoverflow.com/a/13654489/851737 this shouldn't result in a segfault. So it might be a bug in Python. I appended one log (I have various others if you wish to see them) with faulthandler enabled by https://pypi.python.org/pypi/nose-faulthandler.
Yes, I could reproduce segfaults on Python 2.7 (looks like it is even worse than on 2.6 where it appeared only randomly). I was not quite accurate in my initial comment. I don't use any custom C extensions but I'm using pygtk/gobject so it might be a bug there. However, my library contains a coroutine scheduler similar to tulip so it is very likely that this is related to #14432. I'll try that patch and keep you posted.
> I have a core dump, should I upload it? The coredump is not useful if we cannot analyze it. Please open it in gdb, type "thread all apply where" and copy/paste in a file and attach the file. You may use "set pagination off" for easier copy/paste.
Ok, these issues were probably due to the shipped version of PyGTK (which is used as event scheduler). Since I built my own Python and own PyGTK everything looks fine.
History
Date
User
Action
Args
2022-04-11 14:57:49
admin
set
github: 62883
2013-10-30 11:24:10
schlamar
set
status: open -> closedresolution: not a bugmessages: +