public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stefan at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/16592] New: crash in startup
Date: Sat, 15 Feb 2014 01:42:00 -0000 [thread overview]
Message-ID: <bug-16592-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16592
Bug ID: 16592
Summary: crash in startup
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: stefan at codesourcery dot com
Created attachment 7420
--> https://sourceware.org/bugzilla/attachment.cgi?id=7420&action=edit
test case demonstrating the bug
The attached directory contains a testcase for a crash during program startup
when an audit library is used.
To reproduce, run 'make' in the directory to build a small probe application as
well as audit library. Then run 'make run' (after adding '.' to
LD_LIBRARY_PATH) to invoke the probe application with the audit library set, to
observe the crash. (I debugged this by running
.../ld-linux-x86-64.so.2 --audit ldaudit.so ./probe
I could prevent the crash by removing the -llttng-ust argument on the link
command. (In reality I would actually like to use that library. In this test
case I have merely removed any actual use as the crash happens even if the
library is never used at runtime.)
Are there any limitations on what an audit library may link to ?
I'm using gcc 4.8.2 on a Fedora 20 platform (using the system glibc 2.18).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-02-15 1:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 1:42 stefan at codesourcery dot com [this message]
2014-02-15 11:59 ` [Bug dynamic-link/16592] " schwab@linux-m68k.org
2014-02-15 12:53 ` stefan at codesourcery dot com
2014-02-15 14:25 ` schwab@linux-m68k.org
2014-02-15 17:31 ` stefan at codesourcery dot com
2014-02-16 18:10 ` stefan at codesourcery dot com
2014-02-17 4:03 ` carlos at redhat dot com
2014-02-17 22:16 ` stefan at codesourcery dot com
2014-02-18 3:56 ` stefan at codesourcery dot com
2014-02-18 4:08 ` stefan at codesourcery dot com
2014-02-19 5:29 ` carlos at redhat dot com
2014-02-19 5:33 ` stefan at codesourcery dot com
2014-02-19 5:42 ` carlos at redhat dot com
2014-02-19 13:40 ` stefan at codesourcery dot com
2014-02-19 13:45 ` carlos at redhat dot com
2014-02-19 13:51 ` schwab@linux-m68k.org
2014-03-20 21:49 ` stefan at codesourcery dot com
2014-03-26 14:50 ` stefan at codesourcery dot com
2014-04-10 20:32 ` stefan at codesourcery dot com
2014-06-13 8:14 ` fweimer at redhat dot com
2014-06-13 14:59 ` paul_woegerer at mentor dot com
2014-06-13 15:01 ` paul_woegerer at mentor dot com
2014-06-20 15:12 ` stefan at codesourcery 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-16592-131@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: link
Be 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).