public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugzilla at obra dot se" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14035] New: segfault with sound devices / output Date: Sun, 29 Apr 2012 18:59:00 -0000 [thread overview] Message-ID: <bug-14035-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14035 Bug #: 14035 Summary: segfault with sound devices / output Product: glibc Version: 2.15 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: bugzilla@obra.se CC: drepper.fsp@gmail.com Classification: Unclassified Old issue that still remains in 2.15.1, that I couldn't find a bug # for: http://sourceware.org/ml/libc-alpha/2011-06/msg00010.html [PATCH] Fix memory leak on init/fini dependency list http://sourceware.org/ml/libc-hacker/2010-09/msg00009.html [PATCH] Fix memory leak in dlopen with RTLD_NOLOAD http://sourceware.org/ml/libc-hacker/2011-02/msg00004.html -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-04-29 18:59 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-29 18:59 bugzilla at obra dot se [this message] 2012-05-02 10:55 ` [Bug libc/14035] " aj at suse dot de 2014-06-25 11:11 ` fweimer 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=bug-14035-131@http.sourceware.org/bugzilla/ \ --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).