[yocto] Debug with gdbserver

[Khem Raj]

On Jul 31, 2012, at 8:47 PM, Darren Hart <dvhart at linux.intel.com> wrote:

> 
> 
> On 07/31/2012 08:13 PM, Khem Raj wrote:
>> 
>> On Jul 31, 2012, at 7:46 PM, Darren Hart <dvhart at linux.intel.com> wrote:
>> 
>>> I am trying to debug a userpsace application that misbehaves under
>>> poky-tiny. My current approach is use gdbserver on the target and attach
>>> to the offending process, then connect to it on the client using the
>>> yocto-built native gdb for the target.
>>> 
>>> I can easily add gdbserver to the target image, and can successfully
>>> connect it to the process:
>>> 
>>> # From the target (qemux86) root shell:
>>> # dropbearkey -t rsa -f ./rsa
>>> # dropbear -r ./rsa
>>> # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ')
>>> # gdbserver 127.0.0.1:1234 --attach $DBPID
>>> 
>>> Now on the host machine (amd64) I want to:
>>> $ gdb????
>>> (gdb) target extended-remote 127.0.0.1:1234
>>> 
>>> Which package do I need to build to get the appropriate gdb for the host
>>> to remote debug processes on the target?
>> 
>> bake cross-gdb for your arch and use it same way as above
> 
> ERROR: Nothing PROVIDES 'cross-gdb'
> 
> gdb-cross maybe?
> 

I meant cross gdb not the exact recipe name :)


> Ah that gets a lot farther... and then do_compile fails.
> 
> | libgdb.a(python.o): In function `gdbpy_target_wide_charset':
> | python.c:(.text+0x1c7): undefined reference to `PyUnicodeUCS4_Decode'
> 
> And a lot more similar to that. I'm doing this on poky-tiny (so a
> minimal target libc... shouldn't impact native bits though right?


shouldn't it seems you need python native

> 
> 
> Will beat on it some more in the morning.
> 
> -- 
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel