Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: <Richard.Earnshaw@arm.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>,
	<Richard.Earnshaw@arm.com>
Subject: Re: Elf OS ABI Number
Date: Wed, 11 Jun 2003 17:20:00 -0000	[thread overview]
Message-ID: <09cc01c3303d$ca16b550$0202040a@catdog> (raw)
In-Reply-To: <200306111644.h5BGiLB13107@pc960.cambridge.arm.com>

> > Does anyone know how to get one of these?  I was rooting around on
Caldera's
> > website but didn't see anything.  I've realized that we need to have a
> > practical way to identify QNX binaries and this looks like the way to
go.
> >
>
> A fairly common question, to which most times the answer is that you don't
> need one.
>
> You should only be using the OS ABI field if you are changing the meaning
> of the ELF specifics for a processor (new relocs, for example) which a
> linker not trained to recognise these would be unable to handle.  It
> shouldn't be used to represent things that are encoded in the instructions
> inside sections (eg library calls specific to your OS, etc).

Actually, we do have a few things that are different - QNX specific
relocations, different MIPS ABI, etc.  It seems like having the ABI number
can do no harm but can certainly be useful.  The problem with things like
.note sections for identifying binaries is that a stripped binary can no
longer be identified.

cheers,

Kris



  reply	other threads:[~2003-06-11 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 14:00 Kris Warkentin
2003-06-11 14:23 ` Andrew Cagney
2003-06-11 16:44 ` Richard Earnshaw
2003-06-11 17:20   ` Kris Warkentin [this message]
2003-06-12 14:27     ` Richard Earnshaw
2003-06-12 14:46       ` Kris Warkentin
2003-06-12 14:50         ` Kris Warkentin

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='09cc01c3303d$ca16b550$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@sources.redhat.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