Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to get symbolic debugging to work?
Date: Wed, 24 Jun 2009 14:45:01 +0000 (UTC)	[thread overview]
Message-ID: <h1te5d$k62$1@ger.gmane.org> (raw)
In-Reply-To: 1245854121.25464.29.camel@sven

On 2009-06-24, Sven Neumann <s.neumann@raumfeld.com> wrote:
> On Tue, 2009-06-23 at 18:18 +0000, Grant Edwards wrote:
>> On 2009-06-22, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>> 
>>> I've given up temporarily on getting thread support to work in
>>> gdbserver.  Now I'm just trying (and failing) to get basic
>>> symbolic debugging to work.
>> 
>> Gdb 6.8 just plain doesn't work for ARM targets.
>> 
>> I switched to 6.7.1, and it works fine (including debugging
>> multiple threaded apps).
>
> I've now tried this change as well, but it doesn't help with
> our problem. Whatever I try, gdb always immidiately receives
> SIGCHLD and dies:
>
> gdb /usr/bin/image-test 
> GNU gdb 6.7.1
> [...]
> This GDB was configured as "arm-linux-uclibcgnueabi"...

I'm afraid I don't have enough memory to use a target-native
gdb -- I have to use gdbserver on the target and a cross-gdb on
another development host.  IIRC, I'm also using OABI and not
EABI.

> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb) r
> Starting program: /usr/bin/image-test 
> warning: Can not parse XML target description; XML support was disabled
> at compile time
>
> [1]+  Stopped(SIGCHLD)        gdb /usr/bin/image-test
>
> That's the same result that I also got with gdb 6.8, except that I
> didn't get the warning about the XML target description with that
> version.
>
> Our platform is armv5tel with EABI

You could try using gdbserver, but my _guess_ is it's an
EABI/OABI issue.

-- 
Grant Edwards                   grante             Yow! We're going to a
                                  at               new disco!
                               visi.com            

  reply	other threads:[~2009-06-24 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 23:50 [Buildroot] How to get symbolic debugging to work? Grant Edwards
2009-06-23 18:18 ` Grant Edwards
2009-06-24  7:59   ` Sven Neumann
2009-06-24  9:16     ` Bernhard Reutner-Fischer
2009-06-24 14:46       ` Peter Korsgaard
2009-06-24 15:12         ` Bernhard Reutner-Fischer
2009-06-24 14:50       ` Grant Edwards
2009-06-24 14:44     ` Peter Korsgaard
2009-06-24 15:11       ` Grant Edwards
2009-06-24 14:35   ` Sven Neumann
2009-06-24 14:45     ` Grant Edwards [this message]
2009-06-24 16:06       ` Sven Neumann

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='h1te5d$k62$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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