public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1137] New: Fix memory leak and possibly endless loop in `error'
Date: Fri, 29 Jul 2005 23:20:00 -0000	[thread overview]
Message-ID: <20050729232051.1137.roland@gnu.org> (raw)

This trunk patch should go into the 2.3 branch:

2005-07-19  Ulrich Drepper  <drepper@redhat.com>

	* misc/Makefile: Add rules to build and run tst-error1.
	* misc/tst-error1.c: New file.
	* misc/error.c: Fix memory leak and possibly endless loop.

-- 
           Summary: Fix memory leak and possibly endless loop in `error'
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: roland at gnu dot org
        ReportedBy: roland at gnu dot org
                CC: glibc-bugs at sources dot redhat dot com
OtherBugsDependingO 852
             nThis:


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1137

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2005-07-29 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 23:20 roland at gnu dot org [this message]
2005-07-29 23:26 ` [Bug libc/1137] " cvs-commit at gcc dot gnu dot org
2005-07-30 10:02 ` schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de
2005-08-02  3:31 ` cvs-commit at gcc dot gnu dot org
2005-09-25 18:32 ` drepper 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=20050729232051.1137.roland@gnu.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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: 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).