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 21:03:43 +0100 [thread overview]
Message-ID: <20140302210343.7b18de0b@skate> (raw)
In-Reply-To: <20140302194833.GK3874@tarshish>
Dear Baruch Siach,
On Sun, 2 Mar 2014 21:48:33 +0200, Baruch Siach wrote:
> On Sun, Mar 02, 2014 at 04:49:03PM +0000, Oded Hanson wrote:
> > What about the include path when compiling from eclipse ? Any
> > chance its using my host include files ?
>
> This should not happen.
Indeed. Having the cross-compiler include host header files would be
horribly wrong.
> > I can see that its using the cross compiler for sure, but don't
> > see where the include path is set.
>
> The cross gcc uses its sysroot as logical root directory for headers
> and libraries. Buildroot sets gcc sysroot to the staging directory.
> For the internal toolchain sysroot is defined at build time (see
> package/gcc/gcc.mk). For external toolchain sysroot is set on gcc
> command line by the external toolchain wrapper (see
> toolchain/toolchain-external/ext-toolchain-wrapper.c).
Correct. Unless there is a bug, the Eclipse plug-in simply calls the
Buildroot cross-compiler, and the Buildroot cross-compiler already
properly looks in the staging directory (which is its sysroot) for
headers and libraries. I remember testing the Eclipse plugin with
several libraries integrated in the toolchain sysroot, with success.
Oded, can you be more specific about the problems you have seen?
Thanks,
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 20:03 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
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 [this message]
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=20140302210343.7b18de0b@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