public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dwhedon at debian dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/2419] New: broken .eh_frame for one argument syscalls. Date: Sun, 05 Mar 2006 23:50:00 -0000 [thread overview] Message-ID: <20060305235051.2419.dwhedon@debian.org> (raw) The .eh_frame sections for the nptl single argument syscalls (close and fsync) in glibc 2.3.6 are being created incorrectly. Valgrind compains about this, as discussed here: http://sourceforge.net/mailarchive/forum.php?thread_id=7568951&forum_id=32038 valgrind emits the message: DWARF2 CFI reader: unhandled CFI instruction 0:50 on startup of every program linking to the offending object. This creates a lot of noise. readelf agrees that there is a problem with the sections: $ readelf --debug-dump=frames /lib/tls/libc.so.6 > /dev/null unsupported or unknown DW_CFA_50 unsupported or unknown DW_CFA_50 $ The patch I will attach shortly fixes the problem. At least the error message goes away and to me the CFI instructions now look correct. FWIW, I noticed the problem on Debian stable (sarge) and current unstable (sid) but it doesn't look like a Debian only issue. -- Summary: broken .eh_frame for one argument syscalls. Product: glibc Version: 2.3.6 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: dwhedon at debian dot org CC: glibc-bugs at sources dot redhat dot com GCC host triplet: i686-pc-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=2419 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-03-05 23:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-05 23:50 dwhedon at debian dot org [this message] 2006-03-05 23:55 ` [Bug nptl/2419] " dwhedon at debian dot org 2006-04-01 21:48 ` drepper 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=20060305235051.2419.dwhedon@debian.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).