I have come to the conclusion that while it is possible there are bugs
in the libraries I use (libxml2, glib, not yet gtk+), 99 times out of 10
the bug is in my own code, perhaps via stack or heap corruption. A
while back I was pointed at a utility called "valgrind" which I have
found quite useful in finding places where I was using bogus pointers
and just getting lucky most of the time.
If you have valgrind, or something like it, you might want to give that
a shot, see what you can find amiss in your code and see if your SEGV
remains after fixing those issues. If the SEGV remains, then at least
valgrind output will help give more information about the path - as
would say a backtrace from a debugger.
rick jones
_______________________________________________
gtk-list@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gtk-list
