Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #11123

Re: Segmentation Fault on exit

From ron <vacorama@gmail.com>
Newsgroups comp.lang.python
Subject Re: Segmentation Fault on exit
Date 2011-08-10 07:18 -0700
Organization http://groups.google.com
Message-ID <38f2d76e-057f-4d62-9012-e09c18639de9@t7g2000vbv.googlegroups.com> (permalink)
References <mailman.1971.1312626956.1164.python-list@python.org>

Show all headers | View raw


On Aug 6, 6:35 am, Vipul Raheja <vipul.ii...@gmail.com> wrote:
> Hi,
>
> I have wrapped a library from C++ to Python using SWIG. But when I
> import it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting. Following is the log:
>
> vipul@vipul-laptop:~/ossim-svn/src/pyossim/swig$ python
> Python 2.6.6 (r266:84292, Sep 15 2010, 15:52:39)
> [GCC 4.4.5] on linux2
> Type "help", "copyright", "credits" or "license" for more information.>>> import pyossim
>
> * Do some stuff *
> >>> exit()
>
> Segmentation fault
> vipul@vipul-laptop:~/ossim-svn/src/pyossim/swig$
>
> Kindly help.
>
> Thanks and Regards,
> Vipul Raheja

Check out Valgrind.  It's easy to set up, runs like gdb, but keeps
track and flags any offending memory use at the c level. Then just
need to find the calling python code.

Back to comp.lang.python | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Segmentation Fault on exit Vipul Raheja <vipul.iiith@gmail.com> - 2011-08-06 16:05 +0530
  Re: Segmentation Fault on exit Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com> - 2011-08-08 08:56 +0200
  Re: Segmentation Fault on exit ron <vacorama@gmail.com> - 2011-08-10 07:18 -0700

csiph-web