Bug 560425

Summary: [abrt] crash in gnash-1:0.8.6-9.fc12
Product: [Fedora] Fedora Reporter: sly <slybloty>
Component: gnashAssignee: Kevin Kofler <kevin>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jreznik, kevin, pertusus, tomeu
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:c9a204f3112d853f6db3929a154539e3bad2ebe6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-25 13:29:46 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description sly 2010-01-31 11:49:26 EST
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: /usr/bin/gtk-gnash -x 84203179 -j 300 -k 300 -u http://picasaweb.google.com/s/c/bin/slideshow.swf -F 111 -U http://www.passionate-music.com/2009/04/vanessa-longa-v.html -P flashvars=host=picasaweb.google.com&RGB=0x000000&feed=http%3A%2F%2Fpicasaweb.google.com%2Fdata%2Ffeed%2Fapi%2Fuser%2Fsuenmiod%2Falbumid%2F5147421734686039233%3Fkind%3Dphoto%26alt%3Drss -P height=300 -P pluginspage=http://www.macromedia.com/go/getflashplayer -P src=http://picasaweb.google.com/s/c/bin/slideshow.swf -P type=application/x-shockwave-flash -P width=300 -
component: gnash
executable: /usr/bin/gtk-gnash
package: gnash-1:0.8.6-9.fc12
rating: 0
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

BFD: Warning: /var/cache/abrt/ccpp-1264956516-15643/coredump is truncated: expected core file size >= 26963968, found: 26697728.
[New Thread 15671]
Cannot access memory at address 0xb77844f8

Thread 2 (Thread 15671):
#0  0x00c07416 in ?? ()
No symbol table info available.
#1  0x0085a3b1 in ?? ()
No symbol table info available.
#2  0x009f6ce4 in ?? ()
No symbol table info available.
#3  0x08e50ac0 in ?? ()
No symbol table info available.
#4  0xb7520f60 in ?? ()
No symbol table info available.
#5  0x00000000 in ?? ()
No symbol table info available.

Thread 1 (Thread 15643):
Cannot access memory at address 0xbffb53d4
Cannot access memory at address 0xb77844f8
No symbol "__abort_msg" in current context.
Comment 1 sly 2010-01-31 11:49:29 EST
Created attachment 387847 [details]
File: backtrace
Comment 2 Kevin Kofler 2010-01-31 12:25:24 EST
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.)

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

Thank you for the bug report.
Comment 3 Kevin Kofler 2010-03-11 03:39:48 EST
Gnash 0.8.7 is now available as an update for Fedora 13 Alpha, 12 and 11. Is this problem still reproducible after updating?

If it is still reproducible, please report the issue to the upstream Gnash project and provide a bug link in this bug report, as already requested in the initial needinfo request.

If it is no longer reproducible, please report this fact here so that we can close this bug as fixed by 0.8.7.

If you do not reply within 2 weeks, I will be forced to close this bug as INSUFFICIENT_DATA.
Comment 4 Kevin Kofler 2010-03-25 13:29:46 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional