[SciPy-dev] petsc4py support? (segfault)

Robert Kern robert.kern@gmail....
Mon May 19 16:07:22 CDT 2008


On Mon, May 19, 2008 at 4:00 PM, Neilen Marais <nmarais@sun.ac.za> wrote:
> On Mon, 19 May 2008 15:54:24 -0500, Robert Kern wrote:
>
>> However, if you run
>> python under gdb, you can get a backtrace which could help you identify
>> the problem.
>
> Hi Robert,
>
> This is what I see:
>
> $ gdb python
> GNU gdb 6.8-debian
> Copyright (C) 2008 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"...
> (gdb) run
> Starting program: /usr/bin/python
> [Thread debugging using libthread_db enabled]
> Python 2.5.2 (r252:60911, Apr 21 2008, 11:17:30)
> [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> [New Thread 0x7f0b081746e0 (LWP 12261)]
>>>> import petsc4py.PETSc
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7f0b081746e0 (LWP 12261)]
> 0x00007f0b02f38b8b in _int_malloc () from /usr/lib/libopen-pal.so.0
> (gdb)

Whoops! I left out the important bit: Now type "bt" to get a backtrace.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
 -- Umberto Eco


More information about the Scipy-dev mailing list