the bug has been opened on https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/197399 "#0 0xb744b9e4 in readdir () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7982d9d in process_dir (dir=0x85214c0 "/usr/local/man") at rarian-man.c:321 dir_iter = (char **) 0xb7991a44 dirp = (DIR *) 0x0 dp = <value optimized out> buf = {st_dev = 18446744073709551615, __pad1 = 38144, st_ino = 139592752, st_mode = 140823936, st_nlink = 21, st_uid = 3010458296, st_gid = 3075485684, st_rdev = 13209129453286862836, __pad2 = 1072, st_size = -1284508968, st_blksize = -1220368384, st_blocks = -1219477184, st_atim = {tv_sec = 139592752, tv_nsec = -1219481612}, st_mtim = {tv_sec = 139592752, tv_nsec = 139596372}, st_ctim = { tv_sec = 139592744, tv_nsec = -1220527682}, __unused4 = 139592752, __unused5 = 3080203467} current = 140823672 #2 0xb79833ed in rrn_man_init () at rarian-man.c:405 No locals. #3 0xb79836f2 in rrn_man_for_each_in_category (category=0x8525380 "1", funct=0x8065f50 <rrn_add_man_document>, user_data=0x8525620) at rarian-man.c:519 iter = <value optimized out> cat = <value optimized out> #4 0x08066874 in toc_process_man (toc=0x82390b0) at yelp-toc.c:906 sects = (gchar **) 0x85171b8 node = (xmlNodePtr) 0x8525620 sect = (xmlChar *) 0x85255b0 "1 1p 1g 1t" id = (xmlChar *) 0x8525488 "Man-man1" mynode = <value optimized out> priv = (YelpTocPriv *) 0x8239100 i = 1 xpath = (xmlXPathContextPtr) 0x8649f48 obj = (xmlXPathObjectPtr) 0x864bb10 man_doc = (xmlDocPtr) 0x8510c08 parserCtxt = (xmlParserCtxtPtr) 0x850ec00 #5 0xb779f5af in g_thread_create_proxy (data=0xb391bec8) at /build/buildd/glib2.0-2.14.1/glib/gthread.c:635 __PRETTY_FUNCTION__ = "g_thread_create_proxy" #6 0xb760b46b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb74906de in clone () from /lib/tls/i686/cmov/libc.so.6"
Fixed in revision 58 in SVN. Will appear in 0.8.1. 2008-07-29 Don Scorgie <Don@Scorgie.org> * librarian/rarian-man.c: Ensure directories exist before trying to read them bug #15755
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.