Try 'adb dmesg' to grab your recent kernel messages, or open an adb shell and do much of what you can on a normal linux.
It is possible to build native command line tools, adb push them, and execute them but it will require some (a)buse of the ndk toolchain and pushing them to a location where the files will have execute permission on a file system that does not have execution masked. The sdcard probably will not work, unless you have a unix-like filesystem inside of it. On Apr 6, 4:48 pm, mike digioia <mpd...@gmail.com> wrote: > Hi > > I have developed new drivers for my ADB enabled phone device. But I am not > able to debug the kernel changes since my printk messages are not included > in the message log. So the new driver's device may not be on the bus or some > other problem i need to debug. However, ADB does not allow me to even scan > the bus to inspect if the device is present. I attempted to ADB push a copy > of i2cdetect but I am unable to execute this tool from the SD card. I also > attempted to use "bin/emulator" on the build host connected to the device to > bring up a gdb shell. But fails to work. > > I would like to use kgdb. Anyone have any success with this restrained > process of kernel debug? Would love to have a serial port to work with and > JTAG. They are both disable on this device. > > thanks in advance. > > /mpd -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
