bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: objdump segfaults on some .o files (OpenBSD sparc64)


From: Henric Jungheim
Subject: Re: objdump segfaults on some .o files (OpenBSD sparc64)
Date: Wed, 29 Jan 2003 07:36:58 -0800
User-agent: Mutt/1.4i

On Wed, Jan 29, 2003 at 12:52:13PM +0000, Nick Clifton wrote:
> Hi Henric,
> 
> > I compiled binutils-2.13.2.1 on OpenBSD with this gcc (from the tip
> > of the gcc-3_2-branch):
> > 
> > ~/src/build/binutils>egcc --version
> > egcc (GCC) 3.2.2 20030128 (prerelease)
>  
> > The resulting objdump *does* segfault.
> 
> So when the 2.13.2.1 sources are built using gcc 3.2.2 20030128, the
> resulting objdump binary crashes, but when the same sources are built
> using the gcc supplied with FreeBSD 5.0, the resulting objdump does
> not crash.  Is this correct ?
> 
> In which case, this implies a compiler bug, not a binutils bug.

I've run one more test since last.  Let me summarize:

1. OpenBSD's native sparc64 "objdump" crashes.

2. binutils-2.13.2.1 targeted to sparc64-unknowns-openbsd3.2, built
on/with...

Crashes:
sparc64 OpenBSD 3.2-current with native gcc (2.95.3 + some OpenBSD crud)
sparc64 OpenBSD 3.2-current with gcc-3.2.2 20030128

Doesn't crash:
x86 FreeBSD 5.0 w/ native gcc (3.2.1 + some FreeBSD crud, I think)
x86 OpenBSD 3.2-current with native gcc (2.95.3 + some OpenBSD crud)



So, x86-based hosts are ok with both gcc3 and 2.95.  sparc64
OpenBSD crashes with both gcc3 and 2.95.3.  Those are all the 
compilers/platforms I have handy at the moment.


> 
> (For what its worth, I just compiled a sparc64 targeted toolchain
> under Red Hat 8.0 and the resulting objdump did not crash when I fed
> it your busop.o file).

x86 host?

> 
> Anyway, I have no real objection to your patch, and it does appear to
> fix up a possibly illegal memory read, so I will apply it, slightly
> extended as shown below.

Cool.


> 
> Cheers
>         Nick
> 

-- 
address@hidden
http://home.attbi.com/~henric/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]