debug: 0.172
semantic: 0.171
graphic: 0.106
other: 0.104
boot: 0.097
device: 0.069
vnc: 0.052
files: 0.044
PID: 0.040
socket: 0.036
performance: 0.035
network: 0.026
KVM: 0.026
permissions: 0.021
debug: 0.827
PID: 0.027
permissions: 0.025
socket: 0.023
other: 0.019
files: 0.016
performance: 0.013
device: 0.013
semantic: 0.009
network: 0.008
vnc: 0.007
graphic: 0.006
boot: 0.004
KVM: 0.002

QEMU crashed when GDB request a big size variable information

Hello,
My host is Fedora 13. My QEMU version is 0.13.0, I use QEMU with GDB to debug Linux kernel(Version 2.6.36.2).

I use QEMU like this:"qemu -s -S -kernel build/arch/i386/boot/bzImage -hda /dev/zero"
When GDB connected with QEMU, and use gdb command print to look big size variable, the qemu is crash down. for example, when I look a task_struct variable 'init_task'(print init_task ), the qemu produce the below message and exit.

*** stack smashing detected ***: qemu terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x4d)[0x78a31d]
/lib/libc.so.6[0x78a2ca]
qemu[0x8059e21]
qemu[0x805a0cf]
qemu[0x80d12a1]
qemu[0x8189cb8]
qemu[0x818c3b0]
/lib/libc.so.6(__libc_start_main+0xe6)[0x6a8cc6]
...............
adbf7000-adbf8000 rw-p 00000000 00:00 0 
adbf8000-ae3f8000 rw-p 00000000 00:00 0 
ae3f8000-ae742000 rw-p 00000000 00:00 0 
ae742000-ae762000 rw-p 00000000 00:00 0 
ae762000-ae764000 rw-p 00000000 00:00 0 
ae764000-ae784000 rw-p 00000000 00:00 0 
ae784000-ae786000 rw-p 00000000 00:00 0 
ae786000-b6786000 rw-p 00000000 00:00 0 
b6786000-b7894000 rw-p 00000000 00:00 0 
b78aa000-b78ab000 rw-p 00000000 00:00 0 
bfe95000-bfeaa000 rw-p 00000000 00:00 0          [stack]
已放弃 (core dumped)

Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?

[Expired for QEMU because there has been no activity for 60 days.]