Comment 12 for bug 79342

ok, hopefully the attached file should be the one you're looking for. By the
way i must commend you on your commitment to getting this issue sorted. Mind
you i didn't expect to be still at this myself either...

I hope we're there now

C

On 15/01/07, ville palo <email address hidden> wrote:
>
> Yes, after qgo has crashed
> in gdb terminal type:
> bt full <enter>
> info registers <enter>
> thread apply all backtrace <enter>
> quit <enter>
>
> and now you should have a file gdb-qgo.txt and that should
> be attached to this report.
>
> --
> crashed playing computer
> https://launchpad.net/bugs/79342
>

--
+44(0)7886 943 940
www.my.opera.com/livingdaylight

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/games/qgo
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1222707536 (LWP 12028)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Qt: gdb: -nograb added to command-line options.
  Use the -dograb option to enforce grabbing.
(no debugging symbols found)
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222707536 (LWP 12028)]
0xb7280df4 in _IO_str_overflow () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt full
#0 0xb7280df4 in _IO_str_overflow () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
Cannot access memory at address 0xbfc1a838
(gdb) info registers
eax 0x31 49
ecx 0x0 0
edx 0x0 0
ebx 0xb734cff4 -1221275660
esp 0xbfc1a80c 0xbfc1a80c
ebp 0xbfc1a834 0xbfc1a834
esi 0x0 0
edi 0xbfc1ae80 -1077825920
eip 0xb7280df4 0xb7280df4 <_IO_str_overflow+132>
eflags 0x10246 [ PF ZF IF RF ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
(gdb) thread apply all backtrace
Couldn't get registers: No such process.
(gdb) quit
The program is running. Exit anyway? (y or n)