Re: Assert messages.
On Sun, 23 Mar 2003 14:40:44 -0800 Carl B. Constantine [EMAIL PROTECTED] wrote: (dispatcher:1692): Gtk-CRITICAL **: file gtkwidget.c: line 4814 (gtk_widget_set_size_request): assertion `height = -1' failed I came across this one some time ago, it is caused by glade-2 (i am using 1.1.3), which sometimes puts negative sizes in gui generation code. In my case, glade was putting -2, so I suggest you search your code for this, and then you should check all of size-related functions in interface.c (or whatever you named it). -- /~\ The ASCIIAndrej Ticho Kacian [EMAIL PROTECTED] \ / Ribbon Campaign GnuPG public key ID: 7CD93FE2 (pgp.mit.edu) X Against HTML Key fingerprint: / \ Email! E87D 9DEF 2A23 6FFB 7AD9 542F 4253 3A46 7CD9 3FE2 Experience is something you don't get until just after you need it. pgp0.pgp Description: PGP signature
Assert messages.
I'm getting a couple of assert messages in my app kind of all-of-a-sudden as of late. I'm curious what they really mean and how can I track them down. Here are the asserts I'm getting: (dispatcher:1692): Gtk-CRITICAL **: file gtkwidget.c: line 4814 (gtk_widget_set_size_request): assertion `height = -1' failed (dispatcher:1692): Gtk-WARNING **: gtkwidget.c:2653: widget `GtkCheckButton' has no activatable signal toggled without arguments (dispatcher:1692): Gtk-WARNING **: gtkwidget.c:2653: widget `GtkCheckButton' has no activatable signal toggled without arguments The last two seem to relate to a new window I've been working on that includes two checkboxes in it. I've set up signals for these two buttons (using glade) so there is a signal handler specified. I only have code written for one of them at present (testing). The first assert I get from time to time on a couple different windows. They don't seem to be consistant. But I've hard-coded the size of the windows (that is to say I've specified they are not resizable in Glade and I've set a specific size for them in Glade as well). Any ideas/help is greatly appreciated. -- .''`. Carl B. Constantine : :' : [EMAIL PROTECTED] `. `'GnuPG: 135F FC30 7A02 B0EB 61DB 34E3 3AF1 DC6C 9F7A 3FF8 `- Debian GNU/Linux -- The power of freedom pgp0.pgp Description: PGP signature
Re: Assert messages.
* Sven Neumann ([EMAIL PROTECTED]) wrote: Hi, Carl B. Constantine [EMAIL PROTECTED] writes: I'm getting a couple of assert messages in my app kind of all-of-a-sudden as of late. I'm curious what they really mean and how can I track them down. you can force warnings to become fatal by passing --g-fatal-warnings to your GTK+ application. The application will then crash on the first warning message allowing you to examine the cause of the warning in a debugger. That may quit the program, but doesn't really give me any details as to where the program gave those warnings or why or still, what they mean. -- .''`. Carl B. Constantine : :' : [EMAIL PROTECTED] `. `'GnuPG: 135F FC30 7A02 B0EB 61DB 34E3 3AF1 DC6C 9F7A 3FF8 `- Debian GNU/Linux -- The power of freedom pgp0.pgp Description: PGP signature
Re: Assert messages.
Hi, Carl B. Constantine [EMAIL PROTECTED] writes: you can force warnings to become fatal by passing --g-fatal-warnings to your GTK+ application. The application will then crash on the first warning message allowing you to examine the cause of the warning in a debugger. That may quit the program, but doesn't really give me any details as to where the program gave those warnings or why or still, what they mean. that's why I mentioned the use of a debugger. I was assuming you know how to get a stack trace using gdb. Salut, Sven ___ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list
