Segfault from script not printed

[spyder-bot]

From contrebasse on 2014-06-16T08:31:03Z

Spyder Version: 2.3.0rc (3722: r5420c4859aaf )
Python Version: 2.7.6
Qt Version : 4.8.5, PyQt4 (API v2) 4.10.4 on Linux
IPython >=0.13 : 2.0.0 (OK)
pyflakes >=0.5.0: 0.5.0 (OK)
pep8 >=0.6 : 1.4.6 (OK)
pygments >=1.6 : 1.6 (OK)
sphinx >=0.6.6 : 1.2.2 (OK)
psutil >=0.3 : 2.1.1 (OK)
jedi >=0.8.0 : 0.8.0-final0 (OK)
matplotlib >=1.0: 1.3.1 (OK)
sympy >=0.7.0 : 0.7.5 (OK)
pylint >=0.25 : 1.2.1 (OK)

What steps will reproduce the problem?

1. Run a script that produces a segfault or a buserror. It can happen with ctypes, cython, or when writing in a memmap when the disk is full, for example. 2. 3.

What is the expected output? What do you see instead?

When a segfaut occurs in a script launched from a terminal an error is printed, but nothing is visible in a spyder's console.

Please provide any additional information below

.
I also have problem with prints from subprocess that are buffered in spyder but not in a terminal. The two problems could have the same source.

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1851

[spyder-bot]

From ccordoba12 on 2014-08-26T09:46:28Z

Could you try to investigate further where this error is coming from?

Labels: MS-v2.4

[Nodd]

Additional information: the "segmentation fault" message is actually printed by the shell executing the program, not by the program itself, that's why redirecting stdout and stderr is not enough. Spyder has to check the return status of the command to know what the error was, and print a message accordingly.

What I still don't know is how to differentiate a program exiting with a segfault or an exit status.

[ccordoba12]

Closing because the Python console is going to be removed in Spyder 3.2.

Please see issue #4524 for our reasons to do this.