Dear Mr. & Miss,

Thanks in advance your kindly advice.
Recently I try to setup KGDB on my device (Android ARM based), and study the 
following pdf:
http://kernel.org/pub/linux/kernel/people/jwessel/dbg_webinar/State_Of_kernel_debugging_LinuxCon2010.pdf

According to my device only has one serial port, I choose agent-proxy.
The following instructions are what I’ve done:

$ ./agent-proxy 5550^5551 0 /dev/ttyUSB0,115200 &
[1] 17919
$ Agent Proxy 1.96 Started with: 5550^5551 0 /dev/ttyUSB0,115200
Agent Proxy running. pid: 17919
telnet localhost 5550
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

After that, I could see the kernel log appeared, then “echo ttyS0 > 
/sys/module/kgdboc/parameters/kgdboc”
[  877.139512] kgdb: Registered I/O driver kgdboc.

Besides, I try to add my debug port like your pdf page 14 said, however, met 
some troubles:
(gdb) tar rem localhost:5551
Remote debugging using localhost:5551
warning: unrecognized item "qSupported" in "qSupported" response
Malformed response to offset query, qOffsets

Meanwhile, I saw the weird messages from my console port when I typed “tar rem 
…”:
+$Hg0#df+$?#3f+$Hc-1#09-+$qC#b4-+$qAttached#8f$qAttached#8f+$qOffsets#4b++


When I turn on “set debug remote 1”, and “echo g > /proc/sysrq-trigger”(panic 
happen),

the error messages are as attached.

I connect the device to my server via RS-232, and ttyUSB0 was established.
I have no idea which part I need to amend? Please kindly give me some 
suggestions

Thanks,
Ban
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to