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/821] dlclose dependency bugs
Date: Wed, 06 Apr 2005 02:51:00 -0000	[thread overview]
Message-ID: <20050406025142.13012.qmail@sourceware.org> (raw)
In-Reply-To: <20050406003951.821.roland@gnu.org>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-04-06 02:51 -------
Subject: Bug 821

CVSROOT:	/cvs/glibc
Module name:	libc
Branch: 	glibc-2_3-branch
Changes by:	roland@sources.redhat.com	2005-04-06 02:51:35

Added files:
	elf            : unload4.c unload4mod2.c unload4mod3.c 
	                 unload4mod1.c unload4mod4.c 

Log message:
	2005-03-08  Jakub Jelinek  <jakub@redhat.com>
	
	[BZ #821]
	* elf/Makefile: Add rules to build and run unload4 test.
	* elf/unload4.c: New file.
	* elf/unload4mod1.c: New file.
	* elf/unload4mod2.c: New file.
	* elf/unload4mod3.c: New file.
	* elf/unload4mod4.c: New file.

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/elf/unload4.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.6.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/elf/unload4mod2.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.6.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/elf/unload4mod3.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.6.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/elf/unload4mod1.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.6.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/elf/unload4mod4.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=NONE&r2=1.1.6.1



-- 


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

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


  parent reply	other threads:[~2005-04-06  2:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  0:39 [Bug libc/821] New: unload3 test case for dlclose roland at gnu dot org
2005-04-06  1:43 ` [Bug libc/821] " cvs-commit at gcc dot gnu dot org
2005-04-06  1:43 ` cvs-commit at gcc dot gnu dot org
2005-04-06  1:43 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:00 ` [Bug libc/821] dlclose dependency bugs roland at gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:50 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:51 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:51 ` cvs-commit at gcc dot gnu dot org [this message]
2005-04-06  2:51 ` cvs-commit at gcc dot gnu dot org
2005-04-06  2:52 ` roland at gnu dot org

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=20050406025142.13012.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).