Re: [PATCH] Handle PowerPC64 ELFv1 function descriptors in libbacktrace (PR other/82368)

On Thu, Feb 15, 2018 at 11:08:20AM +, Szabolcs Nagy wrote: > > --- libbacktrace/elf.c.jj 2018-02-08 20:46:10.671242369 + > > +++ libbacktrace/elf.c 2018-02-14 08:39:06.674088951 + > ... > > @@ -2857,6 +2889,23 @@ elf_add (struct backtrace_state *state, > >

Re: [PATCH] Handle PowerPC64 ELFv1 function descriptors in libbacktrace (PR other/82368)

On 14/02/18 11:41, Jakub Jelinek wrote: Hi! As mentioned in detail in the PR, PowerPC64 ELFv1 function symbols point to function descriptors in .opd section rather than actual code, and one needs to read the code address from the .opd section in order to associate symbols with .text addresses.

Re: [PATCH] Handle PowerPC64 ELFv1 function descriptors in libbacktrace (PR other/82368)

On Wed, Feb 14, 2018 at 3:41 AM, Jakub Jelinek wrote: > > As mentioned in detail in the PR, PowerPC64 ELFv1 function symbols > point to function descriptors in .opd section rather than actual > code, and one needs to read the code address from the .opd section > in order to

Re: [PATCH] Handle PowerPC64 ELFv1 function descriptors in libbacktrace (PR other/82368)

Hi Jakub, On Wed, Feb 14, 2018 at 12:41:38PM +0100, Jakub Jelinek wrote: > As mentioned in detail in the PR, PowerPC64 ELFv1 function symbols > point to function descriptors in .opd section rather than actual > code, and one needs to read the code address from the .opd section > in order to

[PATCH] Handle PowerPC64 ELFv1 function descriptors in libbacktrace (PR other/82368)

Hi! As mentioned in detail in the PR, PowerPC64 ELFv1 function symbols point to function descriptors in .opd section rather than actual code, and one needs to read the code address from the .opd section in order to associate symbols with .text addresses. Fixed thusly, bootstrapped/regtested on