diff options
| author | Andi Kleen <ak@linux.intel.com> | 2014-03-26 18:45:37 -0400 |
|---|---|---|
| committer | Carlos O'Donell <carlos@redhat.com> | 2014-03-26 23:18:15 -0400 |
| commit | df5b85da90915ce6208ad737807e3d8f2a8fce87 (patch) | |
| tree | 5f9d2d8b2b64d2bc9b36dead2b4d4f89f1e8bc79 /nptl/pthread_condattr_init.c | |
| parent | fbd6b5a4052316f7eb03c4617eebfaafc59dcc06 (diff) | |
| download | glibc-df5b85da90915ce6208ad737807e3d8f2a8fce87.tar glibc-df5b85da90915ce6208ad737807e3d8f2a8fce87.tar.gz glibc-df5b85da90915ce6208ad737807e3d8f2a8fce87.tar.bz2 glibc-df5b85da90915ce6208ad737807e3d8f2a8fce87.zip | |
Fix dwarf2 unwinding through futex functions.
When profiling programs with lock problems with perf record -g dwarf,
libunwind can currently not backtrace through the futex and unlock
functions in pthread. This is because they use out of line sections,
and those are not correctly described in dwarf2 (I believe needs
dwarf3 or 4).
This patch first removes the out of line sections. They only save a
single jump, but cause a lot of pain. Then it converts the now inline
lock code to use the now standard gas .cfi_* commands.
With these changes libunwind/perf can backtrace through the futex
functions now.
Longer term it would be likely better to just use C futex() functions
on x86 like all the other architectures. This would clean the code up
even more.
Diffstat (limited to 'nptl/pthread_condattr_init.c')
0 files changed, 0 insertions, 0 deletions