After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 366510 - crash in Help: searching data
crash in Help: searching data
Status: RESOLVED DUPLICATE of bug 364768
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 21:22 UTC by clflra
Modified: 2006-11-02 15:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description clflra 2006-10-28 21:22:30 UTC
Version: 2.16.1

What were you doing when the application crashed?
searching data


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 134955008 vsize: 0 resident: 134955008 share: 0 rss: 50659328 rss_rlim: 0
CPU usage: start_time: 1162070320 rtime: 0 utime: 488 stime: 0 cutime:459 cstime: 0 timeout: 29 it_real_value: 0 frequency: 45

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227618640 (LWP 5381)]
[New Thread -1270535264 (LWP 5384)]
[New Thread -1247589472 (LWP 5383)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227618640 (LWP 5381))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-28 22:49:03 UTC
Thanks for taking the time to report this bug.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols?

Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks!
Comment 2 Fabio Bonelli 2006-11-02 15:17:03 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

You can attach your stack trace to bug 364768 if you want to.

*** This bug has been marked as a duplicate of 364768 ***