[yocto] Debug with gdbserver

[Darren Hart]

On 08/01/2012 03:34 PM, Khem Raj wrote:
> 
> On Aug 1, 2012, at 10:16 AM, Darren Hart <dvhart at linux.intel.com> wrote:
> 
>>
>>
>> On 08/01/2012 10:09 AM, Khem Raj wrote:
>>> On Wed, Aug 1, 2012 at 9:22 AM, Darren Hart <dvhart at linux.intel.com> wrote:
>>>> (gdb) target extended-remote 127.0.0.1:1234
>>>
>>> this should be ip of target which in your case is qemu prolly
>>> something like 192.168.7.2 or somesuch
>>>
>>
>> I was trying to use the "redir" feature of qemu which supposedly allows
>> you to connect to 1234 on the host instead. After looking at this for a
>> bit and not making any progress, I setup tun/tap networking with qemu
>> and easily connected using the target IP as you mention above. I'd like
>> to understand why redir didn't work - as debugging without a full
>> network on the client would be nice - but for now, I'm moving along.
>>
> 
> well redir is visible to qemu gdb stub not to the software stack that qemu is running
> in your case. although you can use that to debug kernel using qemu. Pass -s option 
> and qemu will boot kernel using gdb stub and you can debug the kernel from address 0
> kind of JTAG debugger for poor :)


Oh. Duh. :-)

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel