Am Mittwoch 23 Mai 2007 12:38 schrieb David Nečas: > On Wed, May 23, 2007 at 12:16:51PM +0200, Guenther Meyer wrote: > > I'm working on a gtk-project for some month; I already solved a lot of > > problems by myself, but I'm still learning. > > But now I have a problem, where I can't find any solution: > > > > In my application there's is one window, when I'm closing it, I always > > can see the following messages: > > > > GLib-GObject-WARNING **: instance of invalid non-instantiatable type > > `(null)' > > > > GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion > > `G_TYPE_CHECK_INSTANCE (instance)' failed > > > > and sometimes the application segfaults after this. > > > > The interesting thing is, that there are other windows, that use exactly > > the same code, but they work without any problems... > > > > any hints or tips? > > Use valgrind. > yes, I already was told that. but it floods me with messages, so I can't make any use of it. is there agood howto or something like that anywhere?
> And use gdb, since you get segfaults, have you tried to at > least print backtrace to see where it crashes? > > gdb program core.12345 > backtrace > yes, but that doesn't really help me... Program received signal SIGSEGV, Segmentation fault. 0x0ef042fc in ?? () from /lib/libc.so.6 (gdb) backtrace #0 0x0ef042fc in ?? () from /lib/libc.so.6 #1 0x0ef041fc in ?? () from /lib/libc.so.6 #2 0x0ef06874 in ?? () from /lib/libc.so.6 #3 0x0ef08ad4 in malloc () from /lib/libc.so.6 #4 0x0f84d2fc in cairo_create () from /usr/lib/libcairo.so.2 #5 0x0fb07f90 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #6 0x0fb08130 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #7 0x0fb09d14 in gdk_window_begin_paint_region () from /usr/lib/libgdk-x11-2.0.so.0 #8 0x0fd250f8 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #9 0x0fb0a1f0 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #10 0x0fb0a4e4 in gdk_window_process_all_updates () from /usr/lib/libgdk-x11-2.0.so.0 #11 0x0fb0a5b0 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #12 0x0f6cbe78 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x0f6ce674 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #14 0x0f6d2308 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0x0f6d2774 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #16 0x0fd25464 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x10016750 in main (argc=1, argv=0x7fac3824) at gpsdrive.c:5825 > You can also make GLib abort (and dump core) on CRITICAL or > WARNING messages using g_log_set_always_fatal() or more > flexibily by setting the G_DEBUG environment variable (see > GLib reference documentation). > > The first two points apply generally, not just to Gtk+ > programs. > > Yeti > > -- > http://gwyddion.net/ > _______________________________________________ > gtk-app-devel-list mailing list > gtk-app-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
_______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
