From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.0.90 available for testing
Date: Fri, 19 Feb 2010 16:26:00 -0000 [thread overview]
Message-ID: <4B7EBB95.1060909@rtems.org> (raw)
In-Reply-To: <20100219012023.GG9752@adacore.com>
On 02/19/2010 02:20 AM, Joel Brobecker wrote:
> Hello,
>
> I have just finished creating the gdb-7.0.90 pre-release.
> It is available for download at the following location:
>
> ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-7.0.90.tar.bz2
>
> A gzip'ed version is also available: gdb-7.0.90.tar.gz.
>
> Please give it a test if you can and report any problems you might find.
While test-building gdb-7.0.90 packages for RTEMS, I noticed gdb's
configure scripts doesn't seem to be detecting invalid targets.
For example configure accepts --target=bfin-rtems4.10 without any
complaint and subsequently builds binaries.
However these binaries fail badly at run-time:
# bfin-rtems4.10-gdb
../../gdb-7.0.90/gdb/arch-utils.c:648: internal-error:
initialize_current_architecture: Selection of initial architecture failed
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
../../gdb-7.0.90/gdb/arch-utils.c:648: internal-error:
initialize_current_architecture: Selection of initial architecture failed
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
Aborted (core dumped)
[A far as bfin-* targets are concerned, this issue already existed in
previous gdb-versions.]
Ralf
next prev parent reply other threads:[~2010-02-19 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 1:20 Joel Brobecker
2010-02-19 16:26 ` Ralf Corsepius [this message]
2010-02-19 16:33 ` Joel Brobecker
2010-02-19 16:44 ` Ralf Corsepius
2010-02-19 16:52 ` Joel Brobecker
2010-02-22 7:29 ` Ralf Corsepius
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=4B7EBB95.1060909@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=brobecker@adacore.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