public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Nagender Telkar <ntelkar@gmail.com>
Cc: gdb@sources.redhat.com, Monika Chaddha <monika@acmet.com>
Subject: Re: internal-error: arm_elf_osabi_sniffer
Date: Wed, 11 Aug 2004 21:54:00 -0000	[thread overview]
Message-ID: <1092261252.28853.674.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <3e59910004081114504fd0740e@mail.gmail.com>

On Wed, 2004-08-11 at 22:50, Nagender Telkar wrote:
> Hello 
> 
> I was compiling my code with RVCT compiler from ARM. I had my debugger
> working at assembly level with ADS1.2. Now, I want it to do the same
> for RVCT compiled code.
> 
> Can it not happen?
> 

Not yet.  Somebody's got to add support for the new ABI, and until GCC
has it (that' getting there) there isn't as much pressure for updating
GDB.

GDB is primarily a debugger for debugging GCC generated code, support
for other compilers tends to come second.

R.
> Thank you,
> Nagender
> 
> On Wed, 11 Aug 2004 22:43:12 +0100, Richard Earnshaw
> <rearnsha@gcc.gnu.org> wrote:
> > On Wed, 2004-08-11 at 21:45, Nagender Telkar wrote:
> > > Hello,
> > >
> > > I am working on gdb 6.0.
> > >
> > > When I do an
> > >
> > > gdb> arm-elf-gdb helloworld.elf
> > >
> > > I get the following error.
> > >
> > > ../../insight-6.0.ori/gdb/arm-tdep.c:2747: internal-error: arm_elf_osabi_sniffer
> > > : Unknown ARM EABI version 0x4000000
> > > 
> > You don't say so, but I guess you are compiling your code with ARM's
> > RVDS compiler...
> > 
> > > I looked into the arm-tdep file in the gdb, it seems to be failing at
> > > the function
> > >
> > > static enum gdb_osabi arm_elf_osabi_sniffer (bfd *abfd)
> > >
> > > where it gets
> > >
> > > unsgined int elfosabi = elf_elfheader (abfd)->e_ident[EI_OSABI];
> > >
> > > The elfosabi is getting set to ELFOSABI_NONE.
> > >
> > > Then it tries to get the eflags as
> > >
> > >  eflags = EF_ARM_EABI_VERSION(elf_elfheader(abfd)->e_flags);
> > >
> > > eflags is not getting set to EF_ARM_EABI_VER1, EF_ARM_EABI_VER2 or
> > > EF_ARM_EABI_UNKNOWN.
> > >
> > > I think that is the problem. Thats the reason it gets to the internal error.
> > 
> > Yep.  GDB doesn't understand the EABI yet (even gdb 6.2 -- gdb 6.0
> > predates the EABI, so has no chance).  Even if it got past this point
> > you'd run into further problems.
> > 
> > R.
> >

  reply	other threads:[~2004-08-11 21:54 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 [this message]
2004-08-11 22:19               ` Nagender Telkar
2004-08-11 22:32                 ` Richard Earnshaw

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=1092261252.28853.674.camel@pc960.cambridge.arm.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=monika@acmet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).