Bug 451488 – crash in Help: searching email setup in...

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 451488 - crash in Help: searching email setup in...


Summary:	crash in Help: searching email setup in...


Status:	RESOLVED INCOMPLETE

Product:	yelp
Classification:	Applications
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-27 06:00 UTC by paul
Modified:	2007-06-30 09:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description paul 2007-06-27 06:00:08 UTC

Version: 2.16.1

What were you doing when the application crashed?
searching email setup info. I can't send to SMTP with evolution email. I searched for 'port: 465'


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

Memory status: size: 136294400 vsize: 0 resident: 136294400 share: 0 rss: 52543488 rss_rlim: 0
CPU usage: start_time: 1182923207 rtime: 0 utime: 7131 stime: 0 cutime:6588 cstime: 0 timeout: 543 it_real_value: 0 frequency: 256

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 -1227929936 (LWP 13384)]
[New Thread -1270101088 (LWP 13391)]
[New Thread -1247614048 (LWP 13388)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 144022

Thread 1 (Thread -1227929936 (LWP 13384))

#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-06-27 13:41:19 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 and
reopen this bug or report a new one. Thanks in advance!

Comment 2 paul 2007-06-29 21:39:49 UTC

(In reply to comment #1)
> 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 and
> reopen this bug or report a new one. Thanks in advance!
> 
Hi,
I can reproduce the crash anytime.
After I run gdb $(which gnome-help) PID it produces a trace but no debugging symbols.
Then I type cont and reproduce the crash it just keeps loading.

(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1227217232 (LWP 14406)]
0xb75526a8 in strcmp () from /lib/tls/i686/cmov/libc.so.6
(gdb) thread apply all bt

+ Trace 144709

Thread 1 (Thread -1227217232 (LWP 14406))

#0 strcmp
from /lib/tls/i686/cmov/libc.so.6
#1 g_str_equal
from /usr/lib/libglib-2.0.so.0
#2 ??
#3 ??


Paul.

Comment 3 palfrey 2007-06-30 09:36:30 UTC

First, have you installed debugging symbols for yelp, glib and gtk? Secondly, can you try getting a trace by running yelp under gdb to start with rather than running gdb *after* it crashes. See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for how to do this. Thanks!