From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Nagender Telkar <ntelkar@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: internal-error: arm_elf_osabi_sniffer
Date: Wed, 11 Aug 2004 22:32:00 -0000 [thread overview]
Message-ID: <1092263552.28853.716.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <3e59910004081115196e9416f8@mail.gmail.com>
On Wed, 2004-08-11 at 23:19, Nagender Telkar wrote:
> Where can I get more information about what ABI stuff is all about,
> and why was the ADS1.2 compiled code working with the gdb and RVCT
> compiled code not.
>
http://www.arm.com/products/DevTools/ABI.html
Describes the AAPCS implemented by RVCT.
Other documents on the Net describe the ATPCS as implemented by ADS1.2
R.
prev parent reply other threads:[~2004-08-11 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 21:15 Determining base address of shared library from core file Bloch, Jack
2004-07-27 22:06 ` Kevin Buettner
2004-08-11 0:02 ` internal-error: arm_elf_osabi_sniffer Nagender Telkar
2004-08-11 7:38 ` Monika Chaddha
2004-08-11 20:45 ` Nagender Telkar
2004-08-11 21:45 ` Richard Earnshaw
2004-08-11 21:50 ` Nagender Telkar
2004-08-11 21:54 ` Richard Earnshaw
2004-08-11 22:19 ` Nagender Telkar
2004-08-11 22:32 ` Richard Earnshaw [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=1092263552.28853.716.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ntelkar@gmail.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