-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
segmentation fault (Trac #197) #795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@teoliphant wrote on 2006-07-21 Please tell us the version of NumPy and Python you are running when reporting a segfault. Also use
|
@nilswagner01 wrote on 2006-07-21 Numpy version 1.1.2878 Scipy version 0.5.0.2115 test_divideerr (numpy.core.tests.test_numeric.test_seterr)Segmentation fault Python 2.4.1 (#1, Sep 12 2005, 23:33:18) [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2 |
@alberts wrote on 2006-07-21 Tests of !NumPy 1.1.2880 pass on Windows and Linux without problems. I'm using Python 2.4.3 in both cases. I also ran the tests through Valgrind 3.1.0 on Linux, and everything seems to be fine. Maybe you have a stale build? Maybe Python 2.4.1 also has thread issues? |
@nilswagner01 wrote on 2006-07-21 I am always doing rm -rf build. BTW is test_divideerr (numpy.core.tests.test_numeric.test_seterr)Segmentation fault a new test ? I didn't get any segfault one week ago. |
@alberts wrote on 2006-07-21 No, that test has been there for a while. That test is pretty simple, so see if you can get it to segfault in a seperate script, and start commenting out lines from the test so that we can see specifically which line is causing it to die. |
@nilswagner01 wrote on 2006-07-21 from numpy.core import * from numpy.random import rand, randint from numpy.testing import * from numpy.core.multiarray import dot as dot_ class test_seterr(NumpyTestCase):
seterr(divide='raise')
if name == 'main':
The problem is seterr(divide='raise') |
@rkern wrote on 2006-07-21 I also get a bus error trying to execute that test on PPC OS X with Python 2.4.1 and r2863. I do not get the error on AMD64 Ubuntu, Python 2.4.3. I'll try with the latest SVN in a bit. And Nils, please read WikiFormatting to properly format code and other such text. Your bug reports are difficult to read. |
Milestone changed to |
@alberts wrote on 2006-07-21 A common element between all the crashers seems to be Python < 2.4.3. |
@teoliphant wrote on 2006-07-24 This crash also happens with Python 2.3. Actually Python 2.4.2 works for me. It is definitely a threading issue. If you remove the threads This is done for Python 2.3 but perhaps the check needs to be extended to anything less than Python 2.4.2 |
trac user AndrewJ wrote on 2006-07-24 I can confirm that the problem goes away on upgrading to 2.4.3 on OSX. Andrew |
@teoliphant wrote on 2006-07-26 I've added a check so that threading is disabled on anything but 2.4.2 and above. |
Original ticket http://projects.scipy.org/numpy/ticket/197 on 2006-07-21 by @nilswagner01, assigned to @teoliphant.
numpy.test(1,10) results in a segfault.
Here is a backtrace
The text was updated successfully, but these errors were encountered: