Well, it isn't very hard to debug the kernel in the emulator.
Configure the kernel by hand to include debugging symbols:
cd kernel
make menuconfig
Select Kernel hacking or whatever it is called and select the item
which says to compile the kernel with debugging info.
make
cd ..
When starting the emulator use sth like: (but change the openbsd refs
to linux)
out/host/openbsd-x86_64/bin/emulator -show-kernel -system out/target/
product/generic -kernel kernel/arch/arm/boot/zImage -logcat *:v -qemu
-monitor telnet::4444,server -s
then it will sit waiting for you to prepare your gdb session:
prebuilt/openbsd-x86_64/toolchain/arm-eabi-4.2.1/bin/arm-eabi-gdb
kernel/vmlinux
(gdb) br sys_execve (or some other place you want to gain control)
(gdb) target remote localhost:1234
and then, in another window, release qemu by attaching to its monitor:
telnet localhost 4444
(qemu) cont
well it's somewhat from memory, but I suspect, the info given will
work with perhaps a few modifications...
I just hope that you are hunting for easier bugs than I am... :-)
Good luck
On Nov 29, 5:47 am, allstars <
allstars....@gmail.com> wrote:
> hi Mike
> so far i just need to trace it by emulator on my PC
> since ....i dont have a msm borad
>
> and i just want to know how to easy-tracing Androidkernel
> for example , its initialization (before Zygote is initialized)
>
> i think it will be efficient if i have adebugger
> rather than just seeing printk by dmesg
>
> thanks
>
> On Nov 22, 4:36 am, "Mike Chan" <
m...@android.com> wrote:
>
> > Perhaps you are referring to the msm_serialdebugger? Which allows one to
> > debug (limited) thekernelover serial on the msm arch.
> > > i think the source forkerneldebuggeris located in /mydroid/system/