<br><br><div class="gmail_quote">On Tue, Jul 3, 2012 at 11:26 AM, Amit Nagal <span dir="ltr"><<a href="mailto:helloin.amit@gmail.com" target="_blank">helloin.amit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Jul 3, 2012 at 11:15 AM, Sannu K <<a href="mailto:sannumail4foss@gmail.com">sannumail4foss@gmail.com</a>> wrote:<br>
><br>
><br>
> On Tue, Jul 3, 2012 at 11:09 AM, Peter Teoh <<a href="mailto:htmldeveloper@gmail.com">htmldeveloper@gmail.com</a>> wrote:<br>
>><br>
>> have not heard of such feature available, but technically, the reason why<br>
>> serial port is important is because it is initialized at a very early stage<br>
>> in linux kernel bootup, and anything that happened before that cannot be<br>
>> analyzed via kgdb as well. i am not sure why u need ethernet. normally<br>
>> my approach is to use VirtualBox running a kernel with kgdb parameters all<br>
>> setup, and then define a virtual serial port in VirtualBox, to connect to a<br>
>> pipe, and then from host OS, use gdb to attach via "target remote" to the<br>
>> virtual terminal, which is created via the "socat" command.<br>
>><br>
>> Search the web for details.<br>
>><br>
>> <a href="http://www.google.com.sg/search?q=socat+virtualbox+serial+kgdb" target="_blank">http://www.google.com.sg/search?q=socat+virtualbox+serial+kgdb</a><br>
>><br>
>><br>
>>><br>
</div><div class="im">>>> _______________________________________________<br>
>>> Kernelnewbies mailing list<br>
>>> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
>>> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Regards,<br>
>> Peter Teoh<br>
>><br>
>> _______________________________________________<br>
>> Kernelnewbies mailing list<br>
>> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
>> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
>><br>
><br>
> Hi Amit,<br>
><br>
> KGDB over ethernet is not merged to linux kernel. It is available as a<br>
> separate patch. Ethernet is very fast compared to serial communication.<br>
> While trying to debug a driver it may not be possible to use virtualbox.<br>
><br>
> Thanks,<br>
> Sannu<br>
<br>
</div>Thanx for all useful insights .<br>
<br>
The reason i want to use ethernet is that on my embedded target serial<br>
port is already used for message<br>
logging purpose . so cannot use serial port for debugging .<br>
<br>
basically i want to put breakpoints at runtime and debug modules .<br>
please suggest me alternative<br>
debug mechanism too especially useful for debugging modules on<br>
embedded targets .<br>
<br>
can i know the exact repository from where i can download kgdboe patch<br>
which i can apply for 2.6.35 kernel onwards or 3.x series kernels .<br>
<br>
<br>
Regards<br>
<span class="HOEnZb"><font color="#888888">Amit Nagal<br>
</font></span></blockquote></div><br>Why not try JTAG? I am not sure of how to use it or whether it is available in your hardware but just suggested if that option is missed.<br><br>Thanks,<br>Sannu<br>