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] crash in startup
Date: Sat, 15 Feb 2014 17:31:00 -0000 [thread overview]
Message-ID: <bug-16592-131-mepKBhyKKe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16592-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=16592
--- Comment #4 from Stefan Seefeld <stefan at codesourcery dot com> ---
On 02/15/2014 09:25 AM, schwab@linux-m68k.org wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=16592
>
> Andreas Schwab <schwab@linux-m68k.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |WAITING
>
> --- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
> Please create a self-contained test case.
Well, the problem seems to be related to loading that particular library
with an auditor lib. I have already tried to reproduce the issue with
other libs, but failed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-15 17:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 1:42 [Bug dynamic-link/16592] New: " stefan at codesourcery dot com
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 [this message]
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-mepKBhyKKe@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).