Android Kernel Debugging -
Android Kernel Debugging -
i have been experimenting getting kgdb
work nexus one.
i have pulled kernel android.git.kernel.org , enabled kgdb
including kgdbts
testing using menuconfig
. built kernel , flashed device (which unlocked rooted , running cyanogenmod 7)
i have followed instructions found on http://bootloader.wikidot.com/android:kgdb enable usb connection deed serial connection required kgdb
(and tested communications ttyacm0
ttygs0
successfully).
the next folders exist indicating kgdboc
, kgdbts
have been built kernel:
/sys/modules/kgdboc/parameters /sys/modules/kgdbts/parameters
the next output dmesg showing kgdbts
testing beingness done show (i think) successful completion of tests:
# dmesg | grep kgdb <6>[ 12.974060] kgdb: registered i/o driver kgdbts. <6>[ 12.981781] kgdbts:run plant , detach test <6>[ 12.995178] kgdbts:run sw breakpoint test <6>[ 13.002441] kgdbts:run bad memory access test <6>[ 13.010864] kgdbts:run singlestep test 1000 iterations <6>[ 13.019042] kgdbts:run singlestep [0/1000] <6>[ 13.077850] kgdbts:run singlestep [100/1000] <6>[ 13.132720] kgdbts:run singlestep [200/1000] <6>[ 13.187500] kgdbts:run singlestep [300/1000] <6>[ 13.242370] kgdbts:run singlestep [400/1000] <6>[ 13.297149] kgdbts:run singlestep [500/1000] <6>[ 13.351928] kgdbts:run singlestep [600/1000] <6>[ 13.406829] kgdbts:run singlestep [700/1000] <6>[ 13.461578] kgdbts:run singlestep [800/1000] <6>[ 13.516540] kgdbts:run singlestep [900/1000] <6>[ 13.570922] kgdbts:run do_fork 100 breakpoints <6>[ 21.117645] kgdb: unregistered i/o driver kgdbts, debugger disabled.
i believe problem running getting kernel trigger kgdb
.
# echo -n g > /proc/sysrq-trigger
just results in dropping me command prompt , (i think) suppose freeze , send prompt on usb beingness used psuedo serial port since phone doesn't have real one.
from gather research prompt supposed trigger allow me issue
(gdb) target remote /dev/ttyacm0
and connect debugging session kernel.
i have tested /proc/sysrq-trigger
b
, c
confirm able pass commands sysrq
.
so question next long winded effort provide much info possible why g
not triggering debugger?
this first effort @ kernel debugging on scheme , have run out of ways phrase search on google turn you. thanks!
(i have tried putting kdgbwait in kernel command line without success believe not yet supported android kernel)
android kernel questions rare on [so], asa nobody else has answered have provided findings on issue. unfortunately don't have nexus 1 test on reply not intended step step resolution of problem, should point in right direction of look.
the useful resource have found on problem in lkml patch dongdong deng, unlikely configuration issue these abundant , well-publicized.
this indicates there problem kernel build. tempted start 1 time again latest versions of cm , see if problem goes away.
failing that, seek reporting cyanogen team , see if known issue or has simple workaround.
as lastly resort seek patch if versions compatible. alternative roll sleeves , start hacking cm kernel incorporate patch.
good luck.
android debugging kernel
Comments
Post a Comment