Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #10975 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2011-08-06 17:52 +0100 |
| Last post | 2011-08-06 17:52 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Segmentation Fault on exit Chris Angelico <rosuav@gmail.com> - 2011-08-06 17:52 +0100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2011-08-06 17:52 +0100 |
| Subject | Re: Segmentation Fault on exit |
| Message-ID | <mailman.1982.1312649524.1164.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web