Package: librarian0
Version: 0.6.0-1
Severity: normal

Hello,

When running yelp, I get this message :

[EMAIL PROTECTED]:~/tmp$ yelp
Xlib: unexpected async reply (sequence 0x3e2)!

and then yelp keeps taking 100% of the CPU.


Running yelp in gdb, I found that there is a segault in librarian0. I've build a dbg package to get a more useful backtrace :

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb3999b90 (LWP 23316)]
0xb774493f in process_check_file () at rarian-info.c:185
185       if (!current_entry->name) {
(gdb) bt
#0  0xb774493f in process_check_file () at rarian-info.c:185
#1  0xb7745499 in rrn_info_init () at rarian-info.c:455
#2  0xb7745a3d in rrn_info_get_categories () at rarian-info.c:557
#3  0x080658e5 in ?? ()
#4  0x085a82d8 in ?? ()
#5  0x085a82d8 in ?? ()
#6  0x08072c8a in ?? ()
#7  0x00004922 in ?? ()
#8  0x082d8088 in ?? ()
#9  0x08544790 in ?? ()
#10 0xb3999398 in ?? ()
#11 0x082d80d8 in ?? ()
#12 0x085a82d8 in ?? ()
#13 0x080db558 in ?? ()
#14 0x08519db0 in ?? ()
#15 0xb77f379c in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x085a34d8 in ?? ()
#17 0xb7602c80 in ?? () from /lib/i686/cmov/libpthread.so.0
#18 0xb39993c8 in ?? ()
#19 0xb77a64ff in g_thread_create_proxy (data=0x1)
   at /tmp/buildd/glib2.0-2.14.2/glib/gthread.c:635
Backtrace stopped: frame did not save the PC
(gdb) p current_entry
$1 = (RrnInfoEntry *) 0x0

Thanks,
Nicolas

-- System Information:
Debian Release: lenny/sid
 APT prefers unstable
 APT policy: (999, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages librarian0 depends on:
ii  libc6                         2.6.1-6    GNU C Library: Shared libraries
ii  libgcc1                       1:4.2.2-3  GCC support library
ii  libstdc++6                    4.2.2-3    The GNU Standard C++ Library v3

librarian0 recommends no packages.

-- no debconf information




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to