From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Cc: Robert Berger
<public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org>
Subject: Re: gdb/gdbserver vs. eclipse
Date: Sat, 05 Sep 2015 18:26:03 +0300 [thread overview]
Message-ID: <55EB098B.7040401@reliableembeddedsystems.com> (raw)
In-Reply-To: <21521607.ihPEg5j6zl@rjs-mbpro.streifs.net>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
Hi,
On 09/05/2015 02:47 AM, Rudolf J Streif wrote:
> Hi Robert,
>
> I am seeing the same thing. I cannot even step into a library function unless
> I check "Load shared library symbols automatically" in Debug Configurations >
> Remote C/C++ Application > <Your Application> > Debugger > Shared Libraries.
This needs to be turned on.
I think I made some progress - see attached image.
As you can see I stepped into printf and friends.
For this to work I needed a few more things:
1) directory needs the be the same on host and target
the executable on the host:
/home/student/BBBworkspace/HelloBBBAutotooled/src/HelloBBBAutotooled
the executable on the target:
/home/student/BBBWorkspace/HelloBBBAutotooled/src/HelloBBBAutotooled
2) .gdbinit
I copied my gdbinit on the host to
/home/student/BBBworkspace/HelloBBBAutotooled/.gdbinit
that's the .gdbinit
# don't use default libs from x86/Ubuntu:
set sysroot /opt/adt-target-sysroot/beagle-bone-black-ml
set solib-absolute-prefix /opt/adt-target-sysroot/beagle-bone-black-ml
set solib-search-path /opt/adt-target-sysroot/beagle-bone-black-ml
# point to the libraries with debug info:
set debug-file-directory
/opt/adt-target-sysroot/beagle-bone-black-ml/usr/lib/debug
# point to the source code:
set substitute-path /usr/src/debug
/opt/adt-target-sysroot/beagle-bone-black-ml/usr/src/debug
set substitute-path /
/opt/adt-target-sysroot/beagle-bone-black-ml/usr/src/debug
3) Once you enter the debug view you need to go to the gdb console and:
source /home/student/BBBworkspace/HelloBBBAutotooled/.gdbinit
This did the trick for me.
Regards,
Robert
...The most likely way for the world to be destroyed, most experts
agree, is by accident. That's where we come in; we're computer
professionals. We cause accidents.
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
[-- Attachment #2: eclipse-debug-system-libs.png --]
[-- Type: image/png, Size: 183960 bytes --]
next prev parent reply other threads:[~2015-09-05 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 21:39 gdb/gdbserver vs. eclipse Robert Berger
2015-09-04 23:47 ` Rudolf J Streif
2015-09-05 15:26 ` Robert Berger [this message]
2015-09-05 16:17 ` Rudolf J Streif
2015-09-05 18:10 ` Robert Berger
2015-09-05 18:17 ` Rudolf J Streif
2015-09-05 18:12 ` Rudolf J Streif
2015-09-06 17:05 ` Robert Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55EB098B.7040401@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=public-gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E@plane.gmane.org \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.