This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR 12887, invalid .eh_frame ld segfault

From: Alan Modra <amodra at gmail dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: binutils at sourceware dot org
Date: Wed, 15 Jun 2011 11:40:41 +0930
Subject: Re: PR 12887, invalid .eh_frame ld segfault
References: <20110614125723.GB4011@bubble.grove.modra.org> <BANLkTimVOXShew63N5UeE353VLjxf17c3A@mail.gmail.com>

On Tue, Jun 14, 2011 at 06:14:39AM -0700, H.J. Lu wrote:
> On Tue, Jun 14, 2011 at 5:57 AM, Alan Modra <amodra@gmail.com> wrote:
> > It's amazing what people manage to feed ld. ?This PR is about a
> > .eh_frame section with SHF_MERGE and SHF_STRINGS set.
> >
> > ? ? ? ?PR ld/12887
> > ? ? ? ?* elf-eh-frame.c (_bfd_elf_parse_eh_frame): Check sec_info_type
> > ? ? ? ?before doing anything.
> > ? ? ? ?(_bfd_elf_discard_section_eh_frame): Likewise.
> >
> 
> Does linker issue any meaningful error/warning messages now?

Not for the testcase in PR12887, and I don't think we should.  If we
start issuing warnings for crazy input it will lead to the expectation
that ld ought to warn for every possible combination of odd input that
doesn't "work" according to naive user expectation.

-- 
Alan Modra
Australia Development Lab, IBM

References:
- PR 12887, invalid .eh_frame ld segfault
  - From: Alan Modra
- Re: PR 12887, invalid .eh_frame ld segfault
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]