abrt 1.0.9 detected a crash. architecture: i686 component: gnash executable: /usr/bin/gtk-gnash global_uuid: 919882f3e9472da65e9cf325e9f68b5042c23e5d kernel: 2.6.32.11-99.fc12.i686.PAE package: gnash-1:0.8.7-1.fc12 rating: 4 reason: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) backtrace ----- BFD: Warning: /var/cache/abrt/ccpp-1272043443-2730/coredump is truncated: expected core file size >= 13955072, found: 61440. [New Thread 2732] Failed to read a valid object file image from memory. 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 0x001d7424 in ?? () Thread 2 (Thread 2732): Cannot access memory at address 0xb367e2f0 Thread 1 (Thread 2730): Cannot access memory at address 0xbfbec3b0 From To Syms Read Shared Object Library 0x0086f830 0x00886d0f 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 0xaaa 2730 edx 0x6 6 ebx 0xaaa 2730 esp 0xbfbec3b0 0xbfbec3b0 ebp 0xbfbec3c8 0xbfbec3c8 esi 0x10b3a8f 17513103 edi 0x10ecff4 17747956 eip 0x1d7424 0x1d7424 eflags 0x200206 [ PF IF ID ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 No function contains program counter for selected frame.
Created attachment 409910 [details] File: backtrace
Thank you for taking the time to report this issue to us. This is an issue which is best addressed by the upstream developers. Please file a report at https://savannah.gnu.org/bugs/?group=gnash (the upstream Gnash bug tracker), and when done add the upstream report info to this report. (Unfortunately, the automated abrt tool cannot do this by itself.) If you do not report this bug upstream, we will be forced to close it as INSUFFICIENT_DATA. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report.
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.