[Numpy-discussion] Segmentation fault with argsort

Skipper Seabold jsseabold@gmail....
Fri Dec 18 12:07:36 CST 2009

On Fri, Dec 18, 2009 at 1:00 PM, Robert Kern <robert.kern@gmail.com> wrote:
> Can you give us a gdb backtrace?

No idea what I'm doing, but I figure I should learn a bit...  Does
this look right?

skipper@linux-desktop:~$ gdb python
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /usr/bin/python...Reading symbols from
(no debugging symbols found)...done.
(gdb) run argsort_seg.py
Starting program: /usr/bin/python argsort_seg.py
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00000000004b499a in _PyArg_ParseTupleAndKeywords_SizeT
(args=0x7ffff7f54ad0, keywords=0x7ffff6d89eb0,
    format=0x7ffff6d9308d "|O&O&O", kwlist=0x7ffff6faa5a0) at
1409    ../Python/getargs.c: No such file or directory.
        in ../Python/getargs.c

More information about the NumPy-Discussion mailing list