Sun 31 Jan 2016 10:31:51 AM UTC, original submission:
This is a spin-off from bug #46949 (framebuffer console restoration issue) comment 3.
Current FrameBuffer Gnash seems to always produce a segmentation fault on
its exit procedure, with backtrace more or less similar to:
The way Gnash exit doesn't seems to significantly change the backtrace. Tested with:
- `fscommand("quit")` ActionScript code when `set ignoreFSCommand` in `~/.gnashrc` is `false`
- `--once` command line option
- SIGINT (via Ctrl+C)
- and SIGTERM (via `killall`)
Log output and detailed GDB backtrace from running `singleframe.swf` (from
file #35320 in bug #46308) using `fb-gnash -vv --once singleframe.swf`
are also attached.
This issue is specific to Gnash's FrameBuffer UI.
GTK, Qt4, SDL, and Dump UI are not affected.
Gnash: 0.8.11dev (git e705394 29-Jan-2016)
Framebuffer: inteldrmfb `/dev/fb0` 1366x768 32-bit
System: Debian GNU/Linux 7.0 Wheezy i386
|