** Description changed:
- gtimer segfaults at startup when run on precise beta, with the following
- info from gdb:
+ Impact: gtimer sometimes fails to start and crashes with a segfault
+
+ Fix: the code does not initialize a variable it later uses causing
+ memory corruption
+
+ TEST CASE:
+ start gtimer
+ a window should show
+
+ sometimes it doesn't crash, running it in valgrind will show an
+ conditional jump on uninitialized memory
+
+ Regression Potential:
+ just setting a variable to NULL, no regressions should be possible.
+
+
+ original report:
+ gtimer segfaults at startup when run on precise beta, with the following info
from gdb:
Program received signal SIGSEGV, Segmentation fault.
create_main_window_menu_bar () at main.c:2055
2055 g_message(gettext("Building menu Failed: %s \n"),
err->message);
My guess is that newer GTK+ does not touch the uninitialized pointer
'err' unless an error actually occurs (whether this is a bug in GTK+ or
by design I don't know). I've attached a patch to fix this, at least
gtimer starts OK with it applied (I don't use it myself so it's hard to
say more). However, similar bugs caused by uninitialized pointers may
lurk elsewhere in the code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974038
Title:
gtimer segfaults at startup (precise)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtimer/+bug/974038/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
