From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation fault while trying to remote debug with GDB and GDBServer
Date: Sun, 2 Mar 2014 14:24:06 +0200 [thread overview]
Message-ID: <20140302122406.GJ3874@tarshish> (raw)
In-Reply-To: <29f88dd2071c483bb7102687088ac6b3@DBXPR07MB142.eurprd07.prod.outlook.com>
Hi Oded,
On Sun, Mar 02, 2014 at 12:06:35PM +0000, Oded Hanson wrote:
> OK... After 1 hour of rebuilding my system back with the internal GLIBC
> toolchain I can say...
>
> Thanks !!! :)
Good to hear. I just want to note again that for correct GDB operation,
setting sysroot is needed for external toolchains as well.
baruch
> Its working. Now I just need to see how to make the eclipse plugin run the
> set sysroot command
>
> -----Original Message-----
> From: Baruch Siach [mailto:baruch at tkos.co.il]
> Sent: Sunday, March 02, 2014 11:12 AM
> To: Oded Hanson
> Cc: buildroot at busybox.net
> Subject: Re: [Buildroot] Segmentation fault while trying to remote debug with GDB and GDBServer
>
> On Sun, Mar 02, 2014 at 07:27:36AM +0000, Oded Hanson wrote:
> > I missed your answer about the GDB.
> >
> > How can I force GDB to use my cross compiler libs instead?
> >
> > The logs you see are from my manually using GDB, which indeed might
> > have not been configured to use the cross compiler libs, however, I
> > get the same problem when using the debugger from eclipse, using the
> > buildroot plugin , which does indeed use the libraries from the cross
> > compiler (at least it should, how can I verify this? )
>
> I'm not familiar with the Eclipse plugin so I can't comment on that. As to
> command line invocation of GDB you can change the sysroot of GDB as I said
> in my original response with:
>
> (gdb) set sysroot /home/oded/Buildroot/buildroot-2013.11/output/staging
>
> GDB uses sysroot to locate your target dynamic linker and libraries.
>
> baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-03-02 12:24 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 [this message]
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
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=20140302122406.GJ3874@tarshish \
--to=baruch@tkos.co.il \
--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