From: Daniel Jacobowitz <drow@false.org>
To: "Vellemans, Noel" <Noel.Vellemans@visionBMS.com>
Cc: gdb@sourceware.org
Subject: Re: GDB/GDBSERVER 6.8 for ARM targets not working ??
Date: Fri, 05 Jun 2009 12:21:00 -0000 [thread overview]
Message-ID: <20090605122050.GA16926@caradoc.them.org> (raw)
In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB6701009339@WETMEX10.loepfe.com>
On Fri, Jun 05, 2009 at 01:03:05PM +0200, Vellemans, Noel wrote:
>
> Hi guy's
>
>
> Took me some time ... But ... just got it working by falling back to
> 6.7.1.
>
>
> So GDB/GDBSERVER 6.8 must be broken for ARM.
It definitely isn't. I used it for months, and similar cases to your
example are in the testsuite. Most ARM/GDB users use GLIBC though.
You're using uClibc; it could be a bug in uClibc triggered by
interaction with the newer gdbserver.
This can be tricky to build and set up; if you're having trouble,
there are lots of places to get a preconfigured working copy, and
even support.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-06-05 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 7:50 Vellemans, Noel
2009-06-05 11:03 ` Vellemans, Noel
2009-06-05 12:21 ` Daniel Jacobowitz [this message]
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=20090605122050.GA16926@caradoc.them.org \
--to=drow@false.org \
--cc=Noel.Vellemans@visionBMS.com \
--cc=gdb@sourceware.org \
/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