Re: internal-error: arm_elf_osabi_sniffer

[Nagender Telkar <ntelkar@gmail.com>]

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.

Thank you,
Nagender

On Wed, 11 Aug 2004 22:54:13 +0100, Richard Earnshaw
<rearnsha@gcc.gnu.org> wrote:
> 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.
> > >
>