On Thu, Feb 28, 2013 at 8:23 AM, Paul Pluzhnikov <ppluzhni...@google.com> wrote: > On Wed, Feb 27, 2013 at 5:52 PM, Ian Lance Taylor <i...@google.com> wrote: > >> I think that the libgcc unwinder only calls malloc if somebody calls >> __register_frame_info. > > So I looked. Indeed it doesn't call malloc in our environment, but > does call dl_iterate_phdr, which is just as deadly.
Hmmm, I guess I can't remember why. dl_iterate_phdr uses a recursive lock so there shouldn't be any deadlock problem. If the problem is the dynamic lookup of the dl_iterate_phdr symbol for lazy PLT evaluation, that could be finessed by calling it beforehand. Ian
