Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Segmentation fault while trying to remote debug with GDB and GDBServer
Date: Wed, 05 Mar 2014 07:42:04 +0100	[thread overview]
Message-ID: <5316C73C.3090804@mind.be> (raw)
In-Reply-To: <20140302172058.5d9a49e1@skate>

On 02/03/14 17:20, Thomas Petazzoni wrote:
> Hello,
> 
> On Sun, 2 Mar 2014 17:10:08 +0100, Thomas Petazzoni wrote:
> 
>> 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.
> 
> Or now that I think of it, maybe Buildroot should itself generate this
> gdbinit file. It may be useful even for users not using Eclipse.

 Even better: buildroot should generate a wrapper (yet another one!) that
passes -ex 'set sysroot ...' when calling cross-gdb.

 Can someone add that to the todo list on the wiki? (I'm currently offline.)

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-03-05  6:42 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 [this message]
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=5316C73C.3090804@mind.be \
    --to=arnout@mind.be \
    --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