GNOME Bugzilla – Bug 336838
Yelp crashes when trying to browse info page for bash
Last modified: 2007-02-21 17:27:01 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/yelp/+bug/36870 "Yelp crashes when trying to browse info page for bash Distribution: Ubuntu 6.04 (dapper) Package: Yelp Severity: major Version: GNOME2.14.0 unspecified Gnome-Distributor: Ubuntu Synopsis: Yelp crashes when trying to browse info page for bash Bugzilla-Product: Yelp Bugzilla-Component: info Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.0) Description: Yelp crashes when trying to browse Bashref Debugging Information: Backtrace was generated from '/usr/bin/yelp' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1211251008 (LWP 7696)] [New Thread -1244992592 (LWP 7703)] [New Thread -1235915856 (LWP 7698)] [New Thread -1214669904 (LWP 7697)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67383
Thread 1 (Thread -1211251008 (LWP 7696))
*** Bug 336948 has been marked as a duplicate of this bug. ***
Confirming. It appears that the tag table in the bash info file assumes there's an extra 3 characters / bytes per section. Yelp uses this offset to look up the page hence, when it is looked up, the offset is out by (3*page_number). No other pages seem to be affected by this but the stand-alone info program deals with this OK, so I guess yelp should too.
A workaround has been committed to HEAD so that when the node isn't found at the offset location, it searches backwards in steps of 3 until it finds it. It shouldn't trip over any previous sections as they are far enough away. This fixes the problem. Closing. 2006-05-11 Don Scorgie <dscorgie@cvs.gnome.org> * src/yelp-info-parser.c: If the node isn't found while parsing, adjust the offset and try again (stupid broken info page workaround) bug #336838
*** Bug 344628 has been marked as a duplicate of this bug. ***
*** Bug 344887 has been marked as a duplicate of this bug. ***
*** Bug 408717 has been marked as a duplicate of this bug. ***
*** Bug 410441 has been marked as a duplicate of this bug. ***