Bug#685589: qsstv: segfault when received image is saved
On Mon, Oct 01, 2012 at 11:37:39AM -0500, Steve Kostecke wrote:
> Could you run qsstv in gdb and capture a back-trace after the segfault?
It seems there are no debugging symbols compiled in, and no qsstv-dbg
package available (I assume that's what I should look for), and I'm not
set up to compile one myself. So I suspect a backtrace from me isn't
worth a whole lot.
$ gdb qsstv
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/qsstv...(no debugging symbols
found)...done.
(gdb) run
Starting program: /usr/bin/qsstv
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb03b4b70 (LWP 7776)]
[New Thread 0xafbb4b70 (LWP 7777)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xafbb4b70 (LWP 7777)]
0x01e352a0 in ?? ()
(gdb) bt
#0 0x01e352a0 in ?? ()
#1 0xafbb42a0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--
Jesper Henriksen
Reply to: