On 04/25/2017 02:49 PM, Mark Wielaard wrote: > From: Ulf Hermann <ulf.herm...@qt.io> > > If we don't find any debug information for a given frame, we usually > cannot unwind any further. However, the binary in question might have > been compiled with frame pointers, in which case we can look up the > well known frame pointer locations in the stack snapshot and use them > to bridge the frames without debug information.
Looks good to me. > +# The binary is generated by compiling with eh_frame CFI, but with frame > +# pointers. > +# > +# gcc -static -O2 -fno-omit-frame-pointer -fno-asynchronous-unwind-tables \ > +# -D_GNU_SOURCE -pthread -o tests/backtrace.aarch64.fp.exec -I. -Ilib \ > +# tests/backtrace-child.c# Trailing '#', but that is insignificant. Ulf
