public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/770] possible deadlock on double-free logging
Date: Sun, 13 Oct 2013 07:36:00 -0000	[thread overview]
Message-ID: <bug-770-131-kvR3PWZGAB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-770-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=770

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |neleai at seznam dot cz
         Resolution|---                         |DUPLICATE

--- Comment #14 from Ondrej Bilka <neleai at seznam dot cz> ---
Fixed in duplicate bug as was mentioned earlier in thread.

*** This bug has been marked as a duplicate of bug 10282 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-10-13  7:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-770-131@http.sourceware.org/bugzilla/>
2011-05-17  2:39 ` [Bug libc/770] " arequipeno at gmail dot com
2011-05-17  2:40 ` arequipeno at gmail dot com
2012-02-21  1:18 ` [Bug malloc/770] " jsm28 at gcc dot gnu.org
2012-04-16 13:49 ` siddhesh at redhat dot com
2012-04-17  4:41 ` arequipeno at gmail dot com
2013-10-13  7:36 ` neleai at seznam dot cz [this message]
2014-02-16 19:20 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-17  4:01 ` 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-770-131-kvR3PWZGAB@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).