Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>,
	Jason R Thorpe <thorpej@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Don't complain about unknown OSABI
Date: Tue, 20 Aug 2002 09:03:00 -0000	[thread overview]
Message-ID: <3D626854.1040500@ges.redhat.com> (raw)
In-Reply-To: <20020820015542.GA12371@nevyn.them.org>


>> GDB uses ../bfd/config.bfd to find the default architecture.  I think 
>> this has made our lives much easier -- gdb's and bfd's defaults match 
>> and we don't have to maintain anything.  It really is a ``free lunch'' :-)
>> 
>> Is there an equivalent for the OS/ABI?  If we can pick that default up 
>> from binutils then we also get that for free.  On the other hand if we 
>> start wiring this stuff into configure.tgt (duplicating ld/gcc) we take 
>> on an additional maintenance task.
> 
> 
> Exactly my point.  There is no OS/ABI equivalent; BFD doesn't know what
> it is, and doesn't need to.
> 
> I'll try to put this together tomorrow.

Ah, M'kay :-)

Next question.  Given an unbranded mips-elf binary, what should the 
following GDB's do?

gdb
mips-linux-gnu-gdb
linux-gnu-gdb
m68k-linux-gnu-gdb
mips-netbsd-gdb
mips-gdb
elf-gdb

Having the behavour key off the target creates a problem with an 
identical executable behaving differently with different, but similar 
GDBs.  I suspect it will encourage people to build different GDB's for 
identical purposes when just a single GDB is needed.

enjoy,
Andrew



  reply	other threads:[~2002-08-20 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  8:41 Andrew Cagney
2002-08-18  8:49 ` Daniel Jacobowitz
2002-08-18  8:54   ` Jason R Thorpe
2002-08-18  9:42   ` Andrew Cagney
2002-08-19  9:15     ` Daniel Jacobowitz
2002-08-19 16:03       ` Andrew Cagney
2002-08-19 16:15         ` Jason R Thorpe
2002-08-19 18:55         ` Daniel Jacobowitz
2002-08-20  9:03           ` Andrew Cagney [this message]
2002-08-20  9:11             ` Daniel Jacobowitz
2002-08-21 10:04               ` Andrew Cagney
2002-08-21 10:08                 ` Daniel Jacobowitz
2002-08-21 10:11                   ` Jason R Thorpe
2002-08-21 13:26                     ` Andrew Cagney
2002-08-21 13:38                       ` Daniel Jacobowitz
2002-08-23  6:07                       ` Richard Earnshaw
2002-08-20  9:22             ` Jason R Thorpe
2002-08-20  9:25               ` Jason R Thorpe
2002-08-18  8:51 ` Jason R Thorpe
2002-08-18  8:52 ` Elena Zannoni
2002-08-18 11:01 ` Andrew Cagney

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=3D626854.1040500@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.com \
    /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