GNOME Bugzilla – Bug 90385
Segmentation fault at startup
Last modified: 2004-12-22 21:47:04 UTC
Package: Yelp Severity: normal Version: 1.0.2 Synopsis: Segmentation fault at startup Bugzilla-Product: Yelp Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.1) Description: Description of Problem: Fatal error (segmentation fault) from Yelp at startup. Steps to reproduce the problem: 1. Selected "Help" from "Applications" Gnome2 menu. 2. 3. Actual Results: Crashed. Expected Results: Help. How often does this happen? Repeatable. Additional Information: Just upgraded to yelp 1.0.2 (along with libgnome 2.0.2 & libgtkhtml 2.0.1). Debugging Information: Backtrace was generated from '/opt/gnome2/bin/yelp' [New Thread 1024 (LWP 17458)] 0x40a49689 in __wait4 () from /lib/libc.so.6
+ Trace 26079
Thread 1 (Thread 1024 (LWP 17458))
0x409f63c0, 0x409f52d8, 0x409f5314, 0x409f5375, 0x409f5381, 0x409f5390, 0x409f5b35, 0x409f5e73, 0x409f6030, 0x409f5d85, 0x409f5e00, 0x409f5e40, 0x409f5f40, 0x409f5c66, 0x409f63c0, 0x409f63c0, 0x409f63c0} step4_jumps = {0x409f63c0 <repeats 14 times>, 0x409f52d8, 0x409f5314, 0x409f5375, 0x409f5381, 0x409f5390, 0x409f5b35, 0x409f5e73, 0x409f6030, 0x409f5d85, 0x409f5e00, 0x409f5e40, 0x409f5f40, 0x409f5c66, 0x409f63c0, 0x409f63c0, 0x409f63c0} is_negative = 1 number = {longlong = 8724520947, word = 134586355} base = 1 the_arg = {pa_char = 216 ' ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-08-10 04:51 ------- The original reporter (dave.bentham@ntlworld.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, micke@codefactory.se.
Yucky. Any clue, Hallski?
Haven't had time to look into this one yet. I'll try to get the time to do so later today.
OK, I think I've found the problem. Looks like I was a bit sloppy while reviewing a patch to fix bug http://bugzilla.gnome.org/show_bug.cgi?id=75728
Fixed in CVS. Hopefully, please reopen if it's not fixed in the next release.
*** Bug 90620 has been marked as a duplicate of this bug. ***
Hallski, is this bug present in the 2.0.1rc1 yelp? should we be pushing a new release for 2.0.1 final?
Done, should be fixed in 1.0.3