[Numpy-discussion] Bus error for Debian / SPARC on current trunk

Mark Wiebe mwwiebe@gmail....
Mon Mar 5 01:53:09 CST 2012

On Sun, Mar 4, 2012 at 10:34 PM, Matthew Brett <matthew.brett@gmail.com>wrote:

> <snip>
> Thanks, that did it:
> 9194b3af704df71aa9b1ff2f53f169848d0f9dc7 is the first bad commit
> Let me know if I can debug further,

That commit was a rewrite of np.concatenate, and I've traced the test
function you got the crash in. The only call to concatenate is as follows:

>>> a = np.array([True], dtype=object)
>>> np.concatenate((a,)*3)
array([True, True, True], dtype=object)

Can you try this and see if it crashes?

Another thing you can do is compile with debug information enabled, then
run the crashing case in gdb. This will look something like this:

$ *export CFLAGS=-g*
$ *rm -rf build* # make sure it's a fresh build from scratch
$ *python setup.py install --prefix=<dir>* # or however you do it
[... build printout]
$ *gdb python <script/options>*
[... gdb info]
(gdb) *run*
 [... script runs]
Program received signal SIGSEGV, Segmentation fault,
[crash address]
(gdb) *backtrace*
[full backtrace printout]

Such a backtrace would be immensely helpful in tracking down why it's


> See you,
> Matthew
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20120304/80911a52/attachment.html 

More information about the NumPy-Discussion mailing list