Bug 626164 - [abrt] google-gadgets-gtk-0.11.2-2.fc13: Process /usr/lib/google-gadgets/gtkmoz-browser-child was killed by signal 6 (SIGABRT)
Summary: [abrt] google-gadgets-gtk-0.11.2-2.fc13: Process /usr/lib/google-gadgets/gtkm...
Keywords:
Status: CLOSED DUPLICATE of bug 590646
Alias: None
Product: Fedora
Classification: Fedora
Component: google-gadgets
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b8f4061012aabdb9d8bd3bb8422...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-22 12:49 UTC by Gerard Barker
Modified: 2010-09-22 20:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-22 20:49:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.38 KB, text/plain)
2010-08-22 12:49 UTC, Gerard Barker
no flags Details

Description Gerard Barker 2010-08-22 12:49:44 UTC
abrt version: 1.1.13
architecture: i686
cmdline: /usr/lib/google-gadgets/gtkmoz-browser-child 12 16
comment: Did nothing except click on a BBC rss feed news item to get summary pop-up.  Abrt reported a crash but the application was fully functional.
component: google-gadgets
crash_function: pthread_cond_timedwait@@GLIBC_2.3.2
executable: /usr/lib/google-gadgets/gtkmoz-browser-child
kernel: 2.6.33.6-147.2.4.fc13.i686.PAE
package: google-gadgets-gtk-0.11.2-2.fc13
rating: 4
reason: Process /usr/lib/google-gadgets/gtkmoz-browser-child was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282473892
uid: 500

backtrace
-----
warning: core file may not match specified executable file.
[New Thread 4355]
[New Thread 4356]
[New Thread 4357]
[New Thread 4358]
[New Thread 4359]
[New Thread 4361]
[New Thread 4363]
Core was generated by `/usr/lib/google-gadgets/gtkmoz-browser-child 12 16'.
Program terminated with signal 6, Aborted.
#0  0x00fab416 in __kernel_vsyscall ()

Thread 7 (Thread 4363):
#0  0x00fab416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00abc5d4 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:236
No locals.
#2  0x05acdbbe in pt_TimedWait (cv=0xa31aec4, ml=0xa31af04, timeout=60000)
    at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:292
        rv = <value optimized out>
        now = {tv_sec = 1282473887, tv_usec = 83469}
        tmo = {tv_sec = 1282473947, tv_nsec = 83469000}
        ticks = <value optimized out>
#3  0x05ace9c7 in PR_WaitCondVar (cvar=0xa31aec0, timeout=60000)
    at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:419
        rv = <value optimized out>
        thred = 0xa236a70
#4  0x05aceac8 in PR_Wait (mon=0xa31af00, timeout=60000)
    at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:601
        rv = -516
        saved_entries = 1
        saved_owner = 3009653616
#5  0x01b46fe1 in Wait (this=0xa31ae80) at ../../dist/include/nsAutoLock.h:340

Timeout exceeded: 60 second, killing gdb

How to reproduce
-----
1. As with earlier 64bit architecture bugreport, this i386 archictecture based report reports the same Abrt crash pop-up and yet the application continues to run without problems.
2.
3.

Comment 1 Gerard Barker 2010-08-22 12:49:47 UTC
Created an attachment (id=440212)
File: backtrace

Comment 2 Peter Robinson 2010-09-22 20:49:09 UTC

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


Note You need to log in before you can comment on or make changes to this bug.