libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Doug Moore
Subject: [Libunwind-devel] unw_get_proc_info is not signal-safe with debug-frames enabled
Date: Thu, 6 Sep 2018 17:55:50 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]