yelp crashed with SIGSEGV in rrn_info_get_categories()

[Phillip Susi]

Binary package hint: yelp

Opened help, there were lots of invalid characters, clicked the home button and it crashed. This is on Maverick.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: yelp 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 20 21:10:56 2010
ExecutablePath: /usr/bin/yelp
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: gnome-help ghelp:user-guide?gospanel-1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa5b9f47fb7: mov 0x0(%r13),%rbp
 PC (0x7fa5b9f47fb7) ok
 source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: yelp
StacktraceTop:
 ?? () from /usr/lib/librarian.so.0
 ?? () from /usr/lib/librarian.so.0
 rrn_info_get_categories () from /usr/lib/librarian.so.0
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
Title: yelp crashed with SIGSEGV in rrn_info_get_categories()
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /usr/lib/librarian.so.0
 ?? () from /usr/lib/librarian.so.0
 rrn_info_get_categories ()
 toc_process_info (toc=0x10519f0) at yelp-toc.c:757
 g_thread_create_proxy (data=0x7fa5a1ca1f30)

[Eliah Kagan (degeneracypressure)]

This bug appears similar to Bug 433504, except in that bug, yelp does not load at all. Inspection of the stack traces reveals the possible similarity.

This bug (and that one) also appear similar to the old bug 375986. That bug is filed against the package rarian, which provides /usr/lib/librarian.so.0 (see this bug's stack trace). Since that old bag appears to be fixed, my guess is that this is not (quite) the same as that.

(I've already commented on Bug 433504 to indicate the similarity, and I'll go ahead and comment on Bug 375896 now.)

[Phillip Susi (psusi)]

Closing bug since it was fixed in the final release.