Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Mon, 22 Feb 2010 07:29:00 -0000	[thread overview]
Message-ID: <4B823249.7020806@rtems.org> (raw)
In-Reply-To: <20100219165223.GF2793@adacore.com>

On 02/19/2010 05:52 PM, Joel Brobecker wrote:
>> I guessed as much - binutils and gcc are more restrictive, ... and
>> unless I am in error, gdb once also was :(
>>      
> I don't remember that it was, but I might be wrong.
Well, in my case, it's only the bfin which exposes this behavior.

IIRC, in case of bfin-* targets, gdb < 7's configure-scripts refused to 
buildbfd, opcodes or some other binutils subdirectory, gdb inherits from 
binutils. AFAIS, gdb >= 7.0 has inherited bfd etc. from a version of 
binutils which has been added the bfin* targets.

I.e. now, binutils' more restrictive checks don't trigger anymore.

>> Note: It did not fail at build-time - Building went absolutely
>> smoothless -- gdb crashed at run-time!
>>      
> Right - I meant run-time, not build-time.
>
> I don't feel like this is a real problem, but others might disagree.
>    
Well, it's certainly not a major issue, nevertheless it's a nuissance 
responsible for nasty surprises and thus should be addressed.

Ralf


      reply	other threads:[~2010-02-22  7:29 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
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 [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=4B823249.7020806@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