public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andris dot zeila at accenture dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11177] New: LD_AUDIT doesn't work with shared libraries containing no code Date: Fri, 15 Jan 2010 11:04:00 -0000 [thread overview] Message-ID: <20100115110434.11177.andris.zeila@accenture.com> (raw) Preface: This issue comes from latrace inability to trace applications built with ICU library for unicode support. Steps to repeat: 1) compile the attached audit library: gcc libaudittest.c -o libaudittest.so --shared 2) compile the attached sample application: gcc audittest.c -o audittest $(icu-config --ldflags) 3) run the resulting application with audit enabled: LD_AUDIT=$(pwd)/libaudittest.so ./audittest Result: ../audittest: no PLTREL found in object /usr/lib/libicudata.so.40 While running just ./audittest works normally. Apparently lbicudata is ICU data only library without any code segments, which confuses glibc. -- Summary: LD_AUDIT doesn't work with shared libraries containing no code Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: andris dot zeila at accenture dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11177 ------- 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:[~2010-01-15 11:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-15 11:04 andris dot zeila at accenture dot com [this message] 2010-01-15 11:05 ` [Bug libc/11177] " andris dot zeila at accenture dot com 2010-01-15 11:05 ` andris dot zeila at accenture dot com 2010-01-15 12:27 ` kirill at shutemov dot name 2010-01-20 2:04 ` drepper at redhat dot com 2010-01-21 15:23 ` eero dot tamminen at nokia dot com 2010-01-27 9:37 ` eero dot tamminen at nokia dot com 2010-01-28 8:17 ` drepper at redhat dot com 2010-02-08 9:03 ` eero dot tamminen at nokia 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=20100115110434.11177.andris.zeila@accenture.com \ --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).