public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-bz at firstfloor dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/15771] __lll_unlock_wake break perf/libunwind unwinding Date: Tue, 23 Jul 2013 06:38:00 -0000 [thread overview] Message-ID: <bug-15771-131-ShSfzTKdx4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15771-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15771 --- Comment #1 from Andi Kleen <andi-bz at firstfloor dot org> --- So it looks like libunwind sometimes gets it right, and sometimes wrong. Depending on the IP hit? Here's the dwarf for __lll_unlock_wake 00002948 00000024 0000294c FDE cie=00000000 pc=0000e090..0000e0ad DW_CFA_advance_loc: 1 to 0000e091 DW_CFA_def_cfa_offset: 16 DW_CFA_advance_loc: 1 to 0000e092 DW_CFA_def_cfa_offset: 24 DW_CFA_offset: r4 (rsi) at cfa-16 DW_CFA_offset: r1 (rdx) at cfa-24 DW_CFA_advance_loc: 25 to 0000e0ab DW_CFA_def_cfa_offset: 16 DW_CFA_restore: r1 (rdx) DW_CFA_advance_loc: 1 to 0000e0ac DW_CFA_def_cfa_offset: 8 DW_CFA_restore: r4 (rsi) DW_CFA_nop DW_CFA_nop DW_CFA_nop DW_CFA_nop DW_CFA_nop and the assembler 000000326fe0de70 <__lll_unlock_wake>: 326fe0de70: 56 push %rsi 326fe0de71: 52 push %rdx 326fe0de72: c7 07 00 00 00 00 movl $0x0,(%rdi) 326fe0de78: 81 f6 81 00 00 00 xor $0x81,%esi 326fe0de7e: ba 01 00 00 00 mov $0x1,%edx 326fe0de83: b8 ca 00 00 00 mov $0xca,%eax 326fe0de88: 0f 05 syscall 326fe0de8a: 5a pop %rdx 326fe0de8b: 5e pop %rsi 326fe0de8c: c3 retq 326fe0de8d: 0f 1f 00 nopl (%rax) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-07-23 6:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-23 4:16 [Bug nptl/15771] New: " andi-bz at firstfloor dot org 2013-07-23 6:38 ` andi-bz at firstfloor dot org [this message] 2014-01-31 7:39 ` [Bug nptl/15771] " arun@sharma-home.net 2014-06-13 13:19 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15771-131-ShSfzTKdx4@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).