GNOME Bugzilla – Bug 316755
assertion failure when running gcalctool
Last modified: 2005-11-03 16:01:59 UTC
Version details: 5.6.31 Distribution/Version: Ubuntu 5.10 run gcalctool from a terminal and see the following output: $ gcalctool (gcalctool:7670): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed
Not enough to go on at the moment. If this is repeatable, could you run gcalctool in the debugger as follows: % gdb gcalctool gdb> run --g-fatal-warnings When it halts with the error, could you print out a stack trace and add it to this bug report? Thanks.
it is always reproducible. Here is the stack trace: Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed aborting... Program received signal SIGABRT, Aborted.
+ Trace 63104
Thread NaN (LWP 7416)
Thanks. When exactly does the error occur? On startup? So does the calculator come up and seem to work okay after the error? Just curious.
The error occurs on startup. The calculator comes up and seems to work okay after the error.
I think I'm now seeing the same thing on Solaris. Well, the stack traces are similar: Gdk-CRITICAL **: file gdkwindow.c: line 2340: assertion `window != NULL' failed aborting... t@1 (l@1) signal ABRT (Abort) in _lwp_kill at 0xcfd75805 0xcfd75805: _lwp_kill+0x0015: jae _lwp_kill+0x23 [ 0xcfd75813, .+0xe ] Current function is scroll_right 2816 gtk_adjustment_set_value(set, set->upper); (dbx) where current thread: t@1 [1] _lwp_kill(0x1, 0x6), at 0xcfd75805 [2] pthread_kill(0x1, 0x6), at 0xcfd72477 [3] raise(0x6), at 0xcfd3d3d3 [4] abort(0x817f5e0, 0x0, 0xd0ffcce0, 0x0, 0xcfdb9000, 0xcfdbd720), at 0xcfd20e00 [5] g_log(0xd0fd0af0, 0x8, 0xd0fd0c74, 0xd0fd0c68, 0x924, 0xd0fd0c58), at 0xcfe25689 [6] gdk_window_invalidate_rect(0x0, 0x0, 0x0), at 0xd0fa1900 [7] gtk_text_view_value_changed(0x817f5e0, 0x819b610), at 0xd0dd337c [8] g_cclosure_marshal_VOID__VOID(0x81978e0, 0x0, 0x1, 0x80467ac, 0x804670c, 0x0), at 0xd006f62d [9] g_closure_invoke(0x81978e0, 0x0, 0x1, 0x80467ac, 0x804670c), at 0xd0059912 [10] signal_emit_unlocked_R(0x817f5b0, 0x0, 0x817f5e0, 0x0, 0x80467ac), at 0xd006eebe [11] g_signal_emit_valist(0x817f5e0, 0xac, 0x0, 0x8046a28), at 0xd006e41e [12] g_signal_emit(0x817f5e0, 0xac, 0x0), at 0xd006e5b8 [13] gtk_adjustment_value_changed(0x817f5e0), at 0xd0c57cd4 [14] gtk_adjustment_set_value(0x817f5e0, 0x0, 0x40690000), at 0xd0c57b98 =>[15] scroll_right(), line 2816 in "gtk.c" [16] set_display(str = 0x8046b17 "0.00", minimize_changes = 0), line 2904 in "gtk.c" [17] create_kframe(), line 1501 in "gtk.c" [18] make_frames(), line 2222 in "gtk.c" [19] do_calctool(argc = 2, argv = 0x8046dcc), line 1186 in "calctool.c" [20] main(argc = 2, argv = 0x8046dcc), line 491 in "gtk.c" (dbx) Investigating now...
Created attachment 54284 [details] Fix for the problem.
Changes checked into CVS HEAD. I've bumped the version number in configure.in to 5.7.10. I'll generate a new tarball in a couple of weeks for the GNOME 2.13.2 release.