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 434266 - crash in Yelp: ???
crash in Yelp: ???
Status: RESOLVED INCOMPLETE
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-29 03:48 UTC by fun_zb
Modified: 2007-06-29 23:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description fun_zb 2007-04-29 03:48:28 UTC 
Version: 2.16.1

What were you doing when the application crashed?
不知道 


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 51752960 vsize: 0 resident: 51752960 share: 0 rss: 5156864 rss_rlim: 0
CPU usage: start_time: 1177818433 rtime: 0 utime: 96 stime: 0 cutime:94 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1244010272 (LWP 28250)]
[New Thread -1248294000 (LWP 28252)]
(no debugging symbols found)
0xb7fad410 in ?? ()

+ Trace 131202







Comment 1


palfrey





          2007-04-29 11:28:37 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


Karsten Bräckelmann





          2007-06-29 23:35:03 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!