Thanks for the suggestion. It was actually something I had never done before, but a little bit of searching on the web showed me how to do it.
In case anyone else is interested, and just to make sure I did it right, here's what I did.
1. I put my test program into a script called 'test_gtkgl.py' 2. In window A, I typed 'python' 3. In window B, I typed 'gdb python <PID of python from window A>' 4. At the gdb prompt in window B, I typed 'cont' 5. In window A I typed 'import test_gtkgl' (which executed the script)' 6. In window B, I got lots of lines that looked like:
Reading symbols for shared libraries . done
and then finally...
Program received signal EXC_BAD_ACCESS, Could not access memory. 0x006a0ee0 in g_type_check_instance_cast () (gdb)
Does this make any sense? Can you offer any suggestions?
On Tuesday, January 20, 2004, at 03:32 PM, Christian Robottom Reis wrote:
On Tue, Jan 20, 2004 at 02:31:27PM -0700, Rick Muller wrote:I'm trying to track down a bug in pygtk. I have a fink installation of
pygtk-2.0.0 (fink is the debian like package manager for Macintosh OS
X). I can currently run all of your demos except for the ones in the gl
subdirectory, which all give a bus error. In fact, I can make it give a
bus error by:gtk.gl.DEPTH_SIZE, 1))import gtk.gl glarea = gtk.gl.Area((gtk.gl.RGBA, gtk.gl.DOUBLEBUFFER,
Can run this through gdb and see why it's blowing up? It could be a simple bug in the PyGTK wrapper..
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
Rick Muller [EMAIL PROTECTED]
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
