This is the mail archive of the mailing list for the glibc 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]

[Bug dynamic-link/21041] Fix for bug 20019 causes linker errors for shared libraries using longjmp

H.J. Lu < at gmail dot com> changed:

           What    |Removed                     |Added
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2017-01-13
     Ever confirmed|0                           |1

--- Comment #9 from H.J. Lu < at gmail dot com> ---
(In reply to Phil Blundell from comment #8)
> (In reply to H.J. Lu from comment #6)
> > I take this back.  Does this testcase ever work after
> > 
> > commit ec2a88b3c659ad4f5a662ca289edae4f0dc19d88
> > Author: Roland McGrath <>
> > Date:   Fri Feb 6 10:53:27 2015 -0800
> > 
> >     Clean up NPTL longjmp to be compat-only.
> > 
> I just did a superficial test with glibc 2.24 and I think you may be right
> that it is broken there too.  In a real application the failure is less
> obvious prior to your patch because it only crashes when longjmp() is
> actually called (which may happen rarely or never) whereas with your patch
> installed the binary won't even start.  But it looks as though it may not
> have worked correctly for some time.

My fix for PR 20019 prevents broken applications from start. It is unsafe
for IFUNC resolver to reference external symbols as shown here.

You are receiving this mail because:
You are on the CC list for the bug.

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