On Wed, Feb 27, 2013 at 2:01 PM, Paul Pluzhnikov <ppluzhni...@google.com> wrote: > > Last I checked, libgcc dwarf handling code called malloc, and thus wasn't > suitable when you want to instrument malloc *itself* to collect stack > traces, nor for SIGPROF profiling. > > Is libgcc dwarf code async-signal safe now? > If not, will it ever be?
I think that the libgcc unwinder only calls malloc if somebody calls __register_frame_info. And in ordinary circumstances nobody ever calls that. I don't think there is an malloc issue there. Unless I've forgotten something. I thought a more serious issue is that the libgcc unwinder has no way of dealing with a corrupt stack--it will simply crash. Ian
