Android's kernel debugger

by allstars » Thu, 20 Nov 2008 07:39:02 GMT


Sponsored Links
 hello world
Android has announced that it enhances support for kernel debugger

where can i find the code for kernel debugger?

i have found other enhancements like alarm, ashmem, binder ,.... etc
but anyway i cannot find kernel debugger

and how should i do to do kernel debugging?
just take qemu for example....
Android has removed the -S option which freezes CPU at start-up

so can someone recommend what to do to kernel-debugging??

thanks





--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



Android's kernel debugger

by Frank Maker » Thu, 20 Nov 2008 16:40:19 GMT


 Where did you see their announcement for enhancing support for kernel 
debugging?

I am also very interested in the best way to do kernel debugging.

-- 
Frank Maker
Graduate Student Researcher
University of California, Davis
Micropower Circuits and Systems Group (MCSG)
[EMAIL PROTECTED]





--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 


Sponsored Links


Android's kernel debugger

by allstars » Fri, 21 Nov 2008 03:03:40 GMT


  http://source.android.com/release-features 

i think the source for kernel debugger is located in /mydroid/system/
core/adb/kdbg.c
and some other files

i just dont know how to use it yet






--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



Android's kernel debugger

by Mike Chan » Fri, 21 Nov 2008 20:36:58 GMT


 Perhaps you are referring to the msm_serial debugger? Which allows one to
debug (limited) the kernel over serial on the msm arch.


CONFIG_MSM_SERIAL_DEBUGGER








-- 
MIke Chan

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



Android's kernel debugger

by allstars » Sat, 29 Nov 2008 04:48:05 GMT


 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 Android kernel
for example , its initialization (before Zygote is initialized)

i think it will be efficient if i have a debugger
rather than just seeing printk by dmesg

thanks






--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



Android's kernel debugger

by Mike Chan » Mon, 01 Dec 2008 17:20:40 GMT


 You probably want kgdb for the goldfish platform, you may have to port kgdb
to the goldfish platform. The patches my apply pretty cleanly though.

So for now, your best bet is printk's. If you do port kgdb to the goldfish
platform please send your patches back to us.










-- 
MIke Chan

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



Android's kernel debugger

by niklas » Sun, 21 Dec 2008 23:48:27 GMT


 ell, 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:47am, allstars <allstars....@gmail.com> wrote:
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Android's kernel debugger

by Niklas Hallqvist » Mon, 22 Dec 2008 00:00:16 GMT


 K, I checked my from memory instructions up, and you
cannot issue the target remote command in gdb, before
you have started qemu from the monitor: so add a quick
(qemu) cont
(qemu) stop
thing in there. Of course that might mean you're missing real early
init, if so, and you need to debug that, you probably need to add -S
support to qemu
again, can't be too hard...

Niklas

niklas wrote:

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Android's kernel debugger

by Dejun Liu » Tue, 30 Dec 2008 14:28:25 GMT


 i all:
Does anyone debug android kernel in qemu successful?,I have tried ,but
failed ,emulator told me that it does not support the qemu option.does
anyone add the qemu option to the android emulator?

steven

2008/12/22 Niklas Hallqvist <niklas+goo...@appli.se<niklas%2bgoo...@appli.se>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Android's kernel debugger

by Niklas Hallqvist » Thu, 01 Jan 2009 11:02:56 GMT


  do it all the time.

Here's a paste of how I start the emulator. If this does no work you
are basing it of a different tree than I (do you use cupcake? maybe it's
changed there?)

/home/projects/android/mydroid/out/host/openbsd-x86_64/bin/emulator
-system out/target/product/generic -kernel kernel/arch/arm/boot/zImage
-show-kernel -logcat *:v -qemu -monitor telnet::4444,server -s

After this the emulator should start waiting for a telnet connection to
port 4444. Then I do:

telnet localhost 4444

and issue the "stop" command immediately. Right after the connect to
4444, the kernel should start listening on port 1234 for an ARM gdb to
attach to.

Niklas

Dejun Liu skrev:


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Android's kernel debugger

by Dejun Liu » Fri, 02 Jan 2009 02:42:56 GMT


 hanks Niklas,

I'm having a holiday now,I will try it later ,thks a lot.

Steven

2009/1/1 Niklas Hallqvist <niklas+goo...@appli.se <niklas%2bgoo...@appli.se>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Is SDK(r2) support camera capture from desktop devices * (webcams etc). ?

Is SDK(second release) support for camera capture from desktop
devices  * ({*filter*}s etc). ? If no
Since real device have its camera. so how should I code for appl which
capture images from camera?

Thank you
--~--~---------~--~----~------------~-------~--~----~

2. Logging to files on the device?

Greetings!

I've been looking at the built in logging classes for Android and am
not sure that it's going to do what I'm after.
We're developing an application where we want the end user to be able
to examine the application log file, and also to be able to send it to
us if there are issues.

The android.util.log class appears to be geared solely towards
debugging on an emulator.  Am I wrong?  Is it possible to specify that
this log is written to a file and then access it externally, copy it,
or even e-mail it?

Alternatively, if I am to write my own log file, or have an
application configuration file, what would be the best place to put
it?  I haven't quite grasped the file system structure yet.  Where
exactly will android.os.Environment.getDataDirectory() point to?  Is
this specific to my application, or all applications? Is it the most
appropriate place to put publicly accessible log files?  Or should I
simply try to create my own directory at the root?

Looking forwards to your suggestions!

--~--~---------~--~----~------------~-------~--~----~

3. Zip inflate failed error while scaning system/app

4. How to Code following logic to make a turning effect of page.

5. Context of a class

6. startup sequence

7. Updated app not showing up in Market's "by date" sorting?