Gtk+-2.0 crashes because you do something wrong. Granted, it would
"nice" that Gtk didn't segfault, but neither PyGTK nor Gtk ever have
given any strict guarantees that erroneous programs don't crash. Either
the bug should be closed, or marked as "enhancement" with minor
severity. It's up to the gtk+ developers whether or not they want to
fix this.
Debugging info why gtk+ crashes:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1211638960 (LWP 8993)]
0xb779d9a0 in widget_add_child_draw_rectangle (widget=0x82cc800,
rect=0xbf887f5c) at gtkwidget.c:2661
2661 if (!GTK_WIDGET_MAPPED (widget) ||
(gdb) l
2656 widget_add_child_draw_rectangle (GtkWidget *widget,
2657 GdkRectangle *rect)
2658 {
2659 GdkRectangle child_rect;
2660
2661 if (!GTK_WIDGET_MAPPED (widget) ||
2662 widget->window != widget->parent->window)
2663 return;
2664
2665 gtk_widget_get_draw_rectangle (widget, &child_rect);
(gdb) p widget->parent
$4 = (GtkWidget *) 0x0
--
buggy PyGTK code crashed the python 2.5 interpreter run via the terminal
https://bugs.launchpad.net/bugs/104980
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
