This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: the setrlimit changes in glibc 2.1.3

To: kukuk at suse dot de
Subject: Re: the setrlimit changes in glibc 2.1.3
From: Mark Kettenis <kettenis at wins dot uva dot nl>
Date: Thu, 13 Jan 2000 15:32:30 +0100 (CET)
CC: hjl at lucon dot org, libc-hacker at sourceware dot cygnus dot com
References: <200001122329.PAA02745@localhost.cygnus.com> <Pine.LNX.4.10.10001121833510.12491-400000@alien.devel.redhat.com> <20000112204122.A17748@lucon.org> <20000113072106.A29543@Wotan.suse.de>

   Date: Thu, 13 Jan 2000 07:21:06 +0100
   From: Thorsten Kukuk <kukuk@suse.de>

   Just curious: I have reported this problem when we have introduced 
   symbol versioning, and everybody here explained me this is the expected
   behaviour because library and main program should never call 2
   different versions of the same function. Now it is a bug ?

No, it's not a bug.  It was designed this way.  As soon as we
introduce a new version for a symbol, the old one will become hidden
and the (static) linker will refuse to use it.

Mark

References:
- Re: the setrlimit changes in glibc 2.1.3
  - From: Cristian Gafton
- Re: the setrlimit changes in glibc 2.1.3
  - From: H . J . Lu
- Re: the setrlimit changes in glibc 2.1.3
  - From: Thorsten Kukuk

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]