From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 66046E00288 for ; Tue, 31 Jul 2012 20:49:36 -0700 (PDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 31 Jul 2012 20:49:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="175548203" Received: from unknown (HELO envy.home) ([10.255.13.49]) by azsmga001.ch.intel.com with ESMTP; 31 Jul 2012 20:49:35 -0700 Message-ID: <5018A6E3.1020704@linux.intel.com> Date: Tue, 31 Jul 2012 20:47:47 -0700 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Khem Raj References: <50189888.3020103@linux.intel.com> In-Reply-To: X-Enigmail-Version: 1.4.3 Cc: Yocto Project Subject: Re: Debug with gdbserver X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2012 03:49:36 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 07/31/2012 08:13 PM, Khem Raj wrote: > > On Jul 31, 2012, at 7:46 PM, Darren Hart 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? 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? Will beat on it some more in the morning. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel