Issue 8976: subprocess module causes segmentation fault (original) (raw)

Created on 2010-06-11 19:21 by Chris.Blazick, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg107573 - (view)	Author: Chris Blazick (Chris.Blazick)	Date: 2010-06-11 19:21
platform: Linux x86_64 (CentOS) kernel: 2.6.18-128.1.10.el5.centos.plus python version: 2.4.3 PyQt versin: 4.7.3 subprocess is generating a segmentation fault. I am running a proprietary quicktime generating script inside my own (Qt) script using the subprocess module. I am piping both stdout and stderr into my script. I have tried reading these two with .communicate() and with the .stdout / .stderr properties. Both end up generating the following error: *** glibc detected *** /usr/bin/python: corrupted double-linked list: 0x00000000161c5c50 *** Segmentation fault running my script, and using os.system() to run the proprietary script works just fine The (C++ compiled) proprietary script does not appear to have any problems crashing under normal circumstances, and I am assuming if there was a problem with the proprietary script, it wouldn't cascade to crashing my own script
msg107585 - (view)	Author: R. David Murray (r.david.murray) *	Date: 2010-06-11 21:07
Well, without a non-proprietary way to reproduce the failure it is going to be a little hard to debug. You could try debugging it with gdb.
msg107604 - (view)	Author: Stefan Krah (skrah) *	Date: 2010-06-11 23:12
> python version: 2.4.3 I'd suggest to try this with Python 2.6 or later. 2.4 and 2.5 are in security-fix only mode.
msg132347 - (view)	Author: Ross Lagerwall (rosslagerwall)	Date: 2011-03-27 16:18
Without more information and a way of reproducing on a recent version of Python, this can't progress. Closing as "works for me".