From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation fault while trying to remote debug with GDB and GDBServer
Date: Sun, 2 Mar 2014 17:10:08 +0100 [thread overview]
Message-ID: <20140302171008.2014a1e0@skate> (raw)
In-Reply-To: <99f27349e290444ba06497af087cb0d8@DBXPR07MB142.eurprd07.prod.outlook.com>
Dear Oded Hanson,
(Adding M?lanie Bats in Cc, since she is responsible for the Eclipse
plugin development)
On Sun, 2 Mar 2014 12:44:23 +0000, Oded Hanson wrote:
> For the completeness of the answer, I will add, that in eclipse plugin you can set the GDB command file. Pointing to a file with the set sysroot command in it, solves the issue also in eclipse and I can debug now from eclipse.
>
> I guess this should be fixed in the eclipse plugin setup.
The Eclipse plugin does set the solib-path (see
https://github.com/mbats/eclipse-buildroot-toolchain-plugin/blob/master/org.buildroot.cdt.toolchain/src/org/buildroot/cdt/toolchain/BuildrootLaunchConfigurationTabGroup.java#L70),
but that is apparently insufficient for gdb to find the correct dynamic
linker, especially when the host and target architectures are identical.
Since there is apparently no way in Eclipse to set a gdb sysroot, I
believe the only solution is for the Eclipse plugin to generate a
simple gdbinit file:
set sysroot /path/to/staging/directory
and then instruct Eclipse to use it.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-02 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ef4c3ec6f84eab802c23a14ecb48ae@DBXPR07MB142.eurprd07.prod.outlook.com>
2014-03-02 7:06 ` [Buildroot] Segmentation fault while trying to remote debug with GDB and GDBServer Baruch Siach
2014-03-02 7:23 ` Oded Hanson
2014-03-02 7:27 ` Oded Hanson
2014-03-02 9:12 ` Baruch Siach
2014-03-02 12:06 ` Oded Hanson
2014-03-02 12:24 ` Baruch Siach
2014-03-02 12:32 ` Oded Hanson
2014-03-02 12:44 ` Oded Hanson
2014-03-02 16:10 ` Thomas Petazzoni [this message]
2014-03-02 16:14 ` Oded Hanson
2014-03-02 16:20 ` Thomas Petazzoni
2014-03-05 6:42 ` Arnout Vandecappelle
2014-03-23 21:07 ` Thomas Petazzoni
2014-03-02 16:49 ` Oded Hanson
2014-03-02 19:48 ` Baruch Siach
2014-03-02 20:03 ` Thomas Petazzoni
2014-03-03 3:42 ` Oded Hanson
2014-02-28 15:58 Oded Hanson
2014-03-02 4:27 ` Baruch Siach
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=20140302171008.2014a1e0@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox