远程'g'数据包回复太长 [英] Remote 'g' packet reply is too long
本文介绍了远程'g'数据包回复太长的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我试图用kvm vm调试Linux内核。我收到一条错误消息Remote'g'数据包回复过长。我的主机是64位,所以是我的vm。
我的步骤:
- 启动gdb
- 执行set architecture i386:x86-64 :intel
- 执行add-symbol-file linux-3.0 / vmlinux
- 执行show arch以验证它仍然是i386: x86-64:intel
- 执行target remote localhost:1234
- 执行continue
- 按Ctrl + C,我得到了上面的消息。
<使用定制内核启动虚拟机,使用-initrd和-append选项。
有没有人遇到过这个问题?对于在运行时在指令集之间切换的cpu,gdb不能很好地工作。等待内核在连接之前提前启动,并且不要使用qemu的 -S
标志。
I am trying to debug Linux kernel with kvm vm. I am getting an error message "Remote 'g' packet reply is too long". My host is 64-bit and so is my vm.
My steps:
- Start the VM with custom -kernel, -initrd and -append options.
- Start gdb
- Execute "set architecture i386:x86-64:intel"
- Execute "add-symbol-file linux-3.0/vmlinux"
- Execute "show arch" to verify its still "i386:x86-64:intel"
- Execute "target remote localhost:1234"
- Execute "continue"
- Press Ctrl+C, I get the above message.
Has anyone faced this problem?
解决方案
gdb doesn't work well against a cpu that switches between instruction sets at runtime. Wait for the kernel to leave early boot before connecting, and don't use qemu's -S
flag.
这篇关于远程'g'数据包回复太长的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文