This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [davidm@napali.hpl.hp.com: Re: [PATCH] i386 vsyscall DSOimplementation]
- From: "H. J. Lu" <hjl at lucon dot org>
- To: Jim Wilson <wilson at tuliptree dot org>
- Cc: binutils at sources dot redhat dot com
- Date: Sat, 14 Jun 2003 21:19:02 -0700
- Subject: Re: [davidm@napali.hpl.hp.com: Re: [PATCH] i386 vsyscall DSOimplementation]
- References: <20030614032158.GA24639@lucon.org> <3EEBA6C7.6010206@tuliptree.org>
On Sat, Jun 14, 2003 at 03:50:47PM -0700, Jim Wilson wrote:
> The patch looks OK to me. Normally this works because unwind info and
> text end up in the same segment. If they end up in different segments,
> then it matters whether we use the segment containing the reloc, or the
> segment containing the symbol. This stuff was written by me, and I
> didn't really know what I was doing at the time.
>
> There does seem to be a technicality here though. The IPF psabi says
> that the reloc is valid only if the symbol and reloc end up in the same
> segment, but they are in different segments here, so technically this is
> invalid. However, there is no problem making this work because the two
> segments have fixed load addresses, so the offsets between the two
> segments will never change. If one of the segments could be loaded at a
> different address, then the offset would change, and the unwind info
> would be incorrect.
Under what condition will the offset between 2 segments change? Even
with shared library, I don't think the offset between 2 segments
will change.
H.J.