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. > > The "unwind" hook is the right place for this as it is so far only > used on s390 and called only after trying to unwind with debug > information.
Looks good to me. Ulf
