It crashes everytime I try to import from math. Is there a way to reinstall the math library? I'm on Python 3.3.2.
sidwyn$ python3
>>> from math import pi
Segmentation fault: 11
Asked
Active
Viewed 3,349 times
5
Sidwyn Koh
- 1,742
- 2
- 21
- 29
-
`math` is a built-in module, I would suggest reinstalling Python, not just that module. – Andrew Clark Sep 04 '13 at 19:38
-
I've tried reinstalling python3, restarting, but nothing seems to solve it. – Sidwyn Koh Sep 04 '13 at 19:39
-
How are you installing, and which platform are you on? – Andrew Clark Sep 04 '13 at 19:41
-
Running the OS X installer from http://www.python.org/download/. – Sidwyn Koh Sep 04 '13 at 19:44
-
Double check the architecture or try installing from source. – Andrew Clark Sep 04 '13 at 19:51
-
What happens if you just `import math`? What's on your `PYTHONPATH`? Any other modules called `math`? – Iguananaut Sep 04 '13 at 19:51
-
1. import math and printing pi causes a segmentation fault. 2.`PYTHONPATH` is empty 3. No other modules called math. – Sidwyn Koh Sep 06 '13 at 02:28
-
Try to see if output of `import math; math.__file__` points to the right location. – cababunga Sep 06 '13 at 23:19
-
You should try printing out a more useful traceback with Python's faulthandler: http://docs.python.org/3/whatsnew/3.3.html#faulthandler – Slater Victoroff Sep 06 '13 at 23:26
-
@cababunga: It does point correctly. Also, I realized that in 90% of cases writing a code in the second line causes it to crash. E.g. any second line of Python code would crash the program. – Sidwyn Koh Sep 06 '13 at 23:28
-
@SlaterTyranus: With the fault handler, it prints out nothing much more: `Fatal Python error: Segmentation fault Current thread 0x00007fff7274b310: Segmentation fault: 11` – Sidwyn Koh Sep 06 '13 at 23:30
-
Can you run it in a debugger to get a stack trace? – cababunga Sep 06 '13 at 23:34
2 Answers
3
Please try this:
$ env -i python3.3
>>> import faulthandler
>>> faulthandler.enable()
>>> import math
>>> math
<module 'math' (built-in)>
>>> from math import pi
# should segfault
and try to run python inside the GNU debugger. You have to type "run" into the gdb shell to start Python and "backtrace" to get the C call stack.
$ gdb python3.3
(gdb) run
>>> from math import pi
# should segfault
(gdb) backtrace
and post the output here.
Christian Heimes
- 1,365
- 10
- 10
1
Turns out it is a Mavericks issue. Should have searched more thoroughly before asking. Sorry.
Duplicate Question: Python crashing when running two commands (Segmentation Fault: 11)
Community
- 1
- 1
Sidwyn Koh
- 1,742
- 2
- 21
- 29