Re: Binutils objcopy bug (was Re: rebase segfault)

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Jan 25 14:19, Kai Tietz wrote:
> 2013/1/25 marco atzeri <marco.atzeri@gmail.com>:
> > On 1/24/2013 11:00 AM, Corinna Vinschen wrote:
> >
> >> I already explained why:  The SEGV happens during relocation.
> >> The file header has been changed already.  If you call the
> >> same rebase, it will try to rebase the file to the same new
> >> address.  If current file base address == requested file base
> >> address, rebase will return without performing any action.
> >>
> >
> > Hi Corinna,
> > I would like your opinion on this .reloc strange issue of
> > dict_snowball, as I have the impression I found the root cause.
> > [...]
> > Questions:
> > - Is it anomalous to have a .reloc portion addressing the
> > debug_* sections (so the original build file is broken)
> > - or should strip recognize and remove reloc portion not
> > anymore relevant ?
> >
> > rebase is choking on this portion of the .reloc table
> >
> >>
> >> Corinna
> >>
> >
> > Thansk in advance
> > Marco
> 
> Well, here are my 2-cents about that issue.  In general it is a flaw
> to have an base-relocation in debug-section, as this means such a
> section can't be moved into a separate debug-file anymore, due that
> has no relocation-information.
> Nevertheless it would be good, if objcopy gets adjusted to eliminated
> base-relocations of stripped sections.

But the tool generating these debug relocs is gas, isn't it?  Why
on earth does it do that?!?

I still think rebase is not to blame here.  It has to assume that
the relocation info is correct, doesn't it?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple