[Ltrace-devel] [PATCH] add library path to stack trace output when using -w
Petr Machata
pmachata at redhat.com
Tue Oct 1 13:45:47 UTC 2013
Petr Machata <pmachata at redhat.com> writes:
> So, how about assuming that everything above the base of a given library
> belongs to that library. That would give us some false positives for
> out-of-bounds IP's, but those are results of a bug anyway.
Except for code generated on stack, when stack is +x. I think nested
functions need +x stack. I'm not sure whether the unwinder would see
those thunks as separate frames though, perhaps it's not really a
problem in practice...
Thanks,
PM
More information about the Ltrace-devel
mailing list