Red Hat Bugzilla – Bug 590320
[abrt] crash in gnash-1:0.8.7-1.fc12: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
Last modified: 2010-12-03 09:55:02 EST
abrt 1.0.9 detected a crash.
cmdline: /usr/bin/gtk-gnash -x 0 -j 0 -k 0 -u about:blank -F 12 -U http://wg198.odnoklassniki.ru/dk;jsessionid=0E50621F0D799E88FC4F12C8A079CF51.wg198?st.cmd=userMain&tkn=2471#st.cmd=userFriendLive -P allowscriptaccess=always -P height=0 -P id=StorageMovie -P src=about:blank -P swliveconnect=0 -P type=application/x-shockwave-flash -P width=0 -
reason: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
BFD: Warning: /var/cache/abrt/ccpp-1273347484-12857/coredump is truncated: expected core file size >= 13365248, found: 1310720.
[New Thread 12859]
Core was generated by `/usr/bin/gtk-gnash -x 0 -j 0 -k 0 -u about:blank -F 12 -U http://wg198.odnoklas'.
Program terminated with signal 6, Aborted.
#0 0x00d40424 in __kernel_vsyscall ()
Thread 2 (Thread 12859):
Cannot access memory at address 0xb356f2f0
Thread 1 (Thread 12857):
Cannot access memory at address 0xbf8a5a5c
From To Syms Read Shared Object Library
0x00ae7830 0x00afed0f Yes (*) /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax 0x0 0
ecx 0x3239 12857
edx 0x6 6
ebx 0x3239 12857
esp 0xbf8a5a50 0xbf8a5a50
ebp 0xbf8a5a68 0xbf8a5a68
esi 0x831a6f 8591983
edi 0x869ff4 8822772
eip 0xd40424 0xd40424 <__kernel_vsyscall+16>
eflags 0x206 [ PF IF ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
Dump of assembler code for function __kernel_vsyscall:
0x00d40414 <__kernel_vsyscall+0>: push %ecx
0x00d40415 <__kernel_vsyscall+1>: push %edx
0x00d40416 <__kernel_vsyscall+2>: push %ebp
0x00d40417 <__kernel_vsyscall+3>: mov %esp,%ebp
0x00d40419 <__kernel_vsyscall+5>: sysenter
0x00d4041b <__kernel_vsyscall+7>: nop
0x00d4041c <__kernel_vsyscall+8>: nop
0x00d4041d <__kernel_vsyscall+9>: nop
0x00d4041e <__kernel_vsyscall+10>: nop
0x00d4041f <__kernel_vsyscall+11>: nop
0x00d40420 <__kernel_vsyscall+12>: nop
0x00d40421 <__kernel_vsyscall+13>: nop
0x00d40422 <__kernel_vsyscall+14>: jmp 0xd40417 <__kernel_vsyscall+3>
0x00d40424 <__kernel_vsyscall+16>: pop %ebp
0x00d40425 <__kernel_vsyscall+17>: pop %edx
0x00d40426 <__kernel_vsyscall+18>: pop %ecx
0x00d40427 <__kernel_vsyscall+19>: ret
End of assembler dump.
Created attachment 412567 [details]
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.