This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug server/13984] gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message
- From: "ciro.santilli at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 12 Aug 2015 12:55:24 +0000
- Subject: [Bug server/13984] gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message
- Auto-submitted: auto-generated
- References: <bug-13984-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13984
Ciro Santilli <ciro.santilli at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ciro.santilli at gmail dot com
--- Comment #4 from Ciro Santilli <ciro.santilli at gmail dot com> ---
@Mehmet can you please make a patch, send to the mailing list, and keep pinging
weekly until it gets reviewed?
I reproduce this by taking the following steps:
# On kernel 4.1, set `CONFIG_DEBUG_INFO` and `CONFIG_GDB_SCRIPTS`.
qemu-system-x86_64 -kernel ../build/arch/x86/boot/bzImage -initrd
rootfs.cpio.gz -S -s
gdb -ex "add-auto-load-safe-path ${vmlinux_path}-gdb.py" \
-ex "file ${vmlinux_path}" \
-ex 'target remote localhost:1234'
hbreak start_kernel
continue
Then the:
Remote 'g' packet reply is too long
message appears, QEMU stops (apparently at the right place) and for most
commands I run, e.g. continue, GDB says:
(gdb) continue
Continuing.
Cannot execute this command while the selected thread is running.
`list` shows the wrong lines, not at `start_kernel` but around line 15. It is
the right file however: `init/main.c`.
If I do Ctrl + D GDB quits and QEMU continues booting as normal.
--
You are receiving this mail because:
You are on the CC list for the bug.