Re: [Libunwind-devel] unw_get_proc_info is not signal-safe with debug-frames enabled

[Sergey Korolev]

Doug,

Can you try this patch?

http://lists.nongnu.org/archive/html/libunwind-devel/2018-06/msg00005.html

пт, 7 сент. 2018 г. в 1:56, Doug Moore <address@hidden>:

It seems that unw_get_proc_info calls dwarf_make_proc_info, calls
fetch_proc_info, calls dwarf_find_proc_info, calls dl_iterate_phdr,
calls dwarf_callback, calls dwarf_find_debug_frame, calls calloc, and
callloc is not signal safe on the aarch64 device I'm testing on.

So would there be a problem with replacing the calloc/realloc memory
management of 'tab' in Gfind_proc_info-lsb.c with mmap and munmap and
memcpy?

Is the memory allocated for 'tab' freed anywhere?  It's not obvious that
it is.

Thanks,

Doug Moore

Rice University


_______________________________________________
Libunwind-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/libunwind-devel