[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [help]While I use qemu and gdb to debug a kernel, it stucks in "[0]k
From: |
Sergio Durigan Junior |
Subject: |
Re: [help]While I use qemu and gdb to debug a kernel, it stucks in "[0]kdb>" and can't enter anything |
Date: |
Fri, 18 Oct 2013 00:40:50 -0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) |
On Sunday, October 13 2013, ZiBin Huang wrote:
> gdb show that the statement that is excuted is
> 93 ret = nb->notifier_call(nb, val, v);
> and qemu just says "[0]kdb>" but i can't type a word in it.
Hard to say without other details.
Is it GDB or kdb? I am not familiar with kdb, and I guess it is
different from GDB. If it is, then you should probably look for help on
kdb related mailing lists.
> When I run :
>
> qemu-system-x86_64 -kernel /home/mm/kdb-work/bzImage -append
> "root=/dev/sda" -boot c -hda /home/mm/kdb-work/busybox.img -k en-us
>
> The qemu starts but it seems that there is a problem because it says
> "Kernel panic -not syncing:No init found"
This seems to be an issue with qemu or with your environment, not
related to GDB too.
--
Sergio