Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #27909 > unrolled thread
| Started by | Vincent Pelletier <plr.vincent@gmail.com> |
|---|---|
| First post | 2012-08-26 09:43 +0200 |
| Last post | 2012-08-26 09:43 +0200 |
| 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: Segfault when setting an instance property on 2.7.3 Vincent Pelletier <plr.vincent@gmail.com> - 2012-08-26 09:43 +0200
| From | Vincent Pelletier <plr.vincent@gmail.com> |
|---|---|
| Date | 2012-08-26 09:43 +0200 |
| Subject | Re: Segfault when setting an instance property on 2.7.3 |
| Message-ID | <mailman.3832.1345967000.4697.python-list@python.org> |
Le samedi 25 août 2012 11:38:47, Vincent Pelletier a écrit :
> Any idea of ways to debug this problem further ?
Trying with pypy ("just to see"), I got even more reproductible segfaults -
even with valgrind.
Turns out, I was not keeping strong references to ctypes buffers, which get
very quickly collected with pypy and memory reused for something else, leading
to a quick crash.
Now, I don't get yet why cpython was not crashing more often, even if I forced
gc.collect() . Less memory recycling maybe ?
Regards,
--
Vincent Pelletier
Back to top | Article view | comp.lang.python
csiph-web