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 411190 - crash in Help: think i put too many wor...
crash in Help: think i put too many wor...
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: 2007-02-23 13:03 UTC by gsthomas76
Modified: 2007-03-04 19:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description gsthomas76 2007-02-23 13:03:28 UTC 
Version: 2.16.1

What were you doing when the application crashed?
think i put too many words into search		


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

Memory status: size: 129404928 vsize: 0 resident: 129404928 share: 0 rss: 47017984 rss_rlim: 0
CPU usage: start_time: 1172235503 rtime: 0 utime: 3042 stime: 0 cutime:2799 cstime: 0 timeout: 243 it_real_value: 0 frequency: 100

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 -1227700560 (LWP 7383)]
[New Thread -1269802080 (LWP 7390)]
[New Thread -1247306848 (LWP 7389)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113209

Thread 1 (Thread -1227700560 (LWP 7383))

  • #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


palfrey





          2007-02-23 14:19:43 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 in advance!







Comment 2


Christian Kirbach





          2007-03-04 19:04:35 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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