On Tue, Jul 3, 2012 at 11:15 AM, Sannu K [off-list ref] wrote:

On Tue, Jul 3, 2012 at 11:09 AM, Peter Teoh [off-list ref] wrote:

quoted

have not heard of such feature available, but technically, the reason why
serial port is important is because it is initialized at a very early stage
in linux kernel bootup, and anything that happened before that cannot be
analyzed via kgdb as well.   i am not sure why u need ethernet.   normally
my approach is to use VirtualBox running a kernel with kgdb parameters all
setup, and then define a virtual serial port in VirtualBox, to connect to a
pipe, and then from host OS, use gdb to attach via "target remote" to the
virtual terminal, which is created via the "socat" command.

Search the web for details.

http://www.google.com.sg/search?q=socat+virtualbox+serial+kgdb

quoted

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Regards,
Peter Teoh

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Hi Amit,

KGDB over ethernet is not merged to linux kernel. It is available as a
separate patch. Ethernet is very fast compared to serial communication.
While trying to debug a driver it may not be possible to use virtualbox.

Thanks,
Sannu

Thanx for all useful insights .

The reason i want to use ethernet is that on my embedded target serial
port is already used for message
logging purpose . so cannot use serial port for debugging .

basically i want to put breakpoints at runtime and debug modules .
please suggest me alternative
debug mechanism too especially useful for debugging modules on
embedded targets .

can i know the exact repository from where i can download kgdboe patch
which i can apply for 2.6.35 kernel onwards or 3.x series kernels .


Regards
Amit Nagal