On Tue, Jan 20, 2004 at 04:31:24PM -0700, Rick Muller wrote:
> Christian,
>
> 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?
It makes sense, but it helps further if:
- You provide a stack trace of the crash (type `where' or `bt' at the
gdb prompt after the crash)
- Your library has symbols compiled in (I'm hoping yours does, but
I'm not very hopeful because the gdb message should have given us
some line information, I think)
Can you open a bug in bugzilla.gnome.org and paste the stack trace in a
comment?
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
