public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1137] Fix memory leak and possibly endless loop in `error'
Date: Fri, 29 Jul 2005 23:26:00 -0000 [thread overview]
Message-ID: <20050729232641.30801.qmail@sourceware.org> (raw)
In-Reply-To: <20050729232051.1137.roland@gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-29 23:26 -------
Subject: Bug 1137
CVSROOT: /cvs/glibc
Module name: libc
Branch: glibc-2_3-branch
Changes by: roland@sources.redhat.com 2005-07-29 23:26:19
Modified files:
misc : error.c Makefile
Added files:
misc : tst-error1.c
Log message:
2005-07-19 Ulrich Drepper <drepper@redhat.com>
[BZ #1137]
* 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.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/misc/tst-error1.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.4.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/misc/error.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.34&r2=1.34.4.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/misc/Makefile.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.112&r2=1.112.4.1
--
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.
next prev parent reply other threads:[~2005-07-29 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 23:20 [Bug libc/1137] New: " roland at gnu dot org
2005-07-29 23:26 ` cvs-commit at gcc dot gnu dot org [this message]
2005-07-30 10:02 ` [Bug libc/1137] " 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=20050729232641.30801.qmail@sourceware.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).