This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/16592] New: crash in startup


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]