Re: Segmentation Fault on exit

References	<CANMJH-t13ntKy1cVmOZ6kmON3_aQoO2BZ=4trO5bz7haHyJDHQ@mail.gmail.com> <CAPTjJmrpYzEAzjyFODzkYBGw2fMiWZr_8y3Wd5VtpZ2iwcTSGQ@mail.gmail.com> <CANMJH-vS-rg=FV90Eti9bdETfPDj=Sfa2NOwVXOC4aXWJ_piGQ@mail.gmail.com> <CAPTjJmqHvJ-YOA53B_1ohwgYyUy8WgM-eXOaWcjWbQbS7aw_pg@mail.gmail.com> <CANMJH-uhEBqp3imj9j_yBRuafJDuFOhJRyx8qmxcfShZHdG=Zw@mail.gmail.com>
Date	2011-08-06 17:52 +0100
Subject	Re: Segmentation Fault on exit
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.1982.1312649524.1164.python-list@python.org> (permalink)

Show all headers | View raw

On Sat, Aug 6, 2011 at 2:34 PM, Vipul Raheja <vipul.iiith@gmail.com> wrote:
> Here's the link: www.geofemengineering.it/data/master_wrap.cxx
> Thanks and Regards,
> Vipul Raheja

Ugh. Unfortunately that file is somewhat lengthy... I hate to say
"tl;dr" to people, but... is there any way to simplify that down?

Perhaps the best way to proceed would be to make a completely empty
SWIG-Python module, with absolutely none of the actual interface code,
just initializing itself and cleaning up. If that doesn't crash, add
code back in until it crashes on exit again.

Alternatively, you may be able to get good results by compiling a
debug build of Python, with reference tracking. I've never done that
myself, but others on this list will be able to advise.

ChrisA

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

Thread

Re: Segmentation Fault on exit Chris Angelico <rosuav@gmail.com> - 2011-08-06 17:52 +0100

csiph-web