Bug 559133 - [abrt] crash in transmission-1.76-1.fc12
Summary: [abrt] crash in transmission-1.76-1.fc12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: transmission
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0b15c6a3cb248766f11290abc54...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-27 09:00 UTC by frogjaw
Modified: 2010-02-17 06:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-17 06:32:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (699 bytes, text/plain)
2010-01-27 09:00 UTC, frogjaw
no flags Details

Description frogjaw 2010-01-27 09:00:09 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: transmission
component: transmission
executable: /usr/bin/transmission
kernel: 2.6.31.9-174.fc12.i686
package: transmission-1.76-1.fc12
rating: 0
reason: Process was terminated by signal 6
release: Fedora release 12 (Constantine)

backtrace
-----
warning: exec file is newer than core file.
Cannot access memory at address 0x28

Thread 1 (Thread 4334):
#0  0x00323416 in ?? ()
No symbol table info available.
#1  0x00b43a81 in ?? ()
No symbol table info available.
#2  0x00c89ff4 in ?? ()
No symbol table info available.
#3  0xbfc7f820 in ?? ()
No symbol table info available.
#4  0xbfc7f828 in ?? ()
No symbol table info available.
#5  0x00b4534a in ?? ()
No symbol table info available.
#6  0x00000006 in ?? ()
No symbol table info available.
#7  0xbfc7f7a0 in ?? ()
No symbol table info available.
#8  0x00000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x28
No symbol table is loaded.  Use the "file" command.

Comment 1 frogjaw 2010-01-27 09:00:12 UTC
Created attachment 387016 [details]
File: backtrace

Comment 2 Rahul Sundaram 2010-02-17 06:32:48 UTC
1.90 release is now available for testing in the repo which should fix this problem


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