[pygtk] Apparent PyGTK Segmentation Fault

[Casey McGinty]

Thanks for the confirmation. Unfortunately that just widens the scope of my
problem to the following modules  ;-)

logging, atexit, dbus, gobject, gconf, pango

Will valgrind or similar tool be able to point to narrow down the search?
I'm leaning towards gobject or gconf.

- Casey

On Thu, Aug 21, 2008 at 4:46 AM, Stephen Langer <stephen.langer at nist.gov>wrote:

> We've seen similar problems.  My guess is that you have a stray pointer in
> a C or C++ extension module which is trashing some part of python's memory.
>  The first time you run the program after modifying it, python is creating
> .pyc files and so its memory usage is different from the second time, when
> it's not creating the files.  Try removing the .pyc files and running again,
> without modifying the code.  It probably won't crash.
>
>  -- Steve
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daa.com.au/pipermail/pygtk/attachments/20080822/b41d5e19/attachment.htm