This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: DLOPEN and Statically linked executable

From: Wolfram Gloger <Wolfram dot Gloger at dent dot med dot uni-muenchen dot de>
To: jeroen at dekkers dot cx
Cc: peter at mysql dot com, sjmunroe at us dot ibm dot com, libc-alpha at sources dot redhat dot com
Date: Fri, 21 Jun 2002 11:31:49 +0200 (MDT)
Subject: Re: DLOPEN and Statically linked executable
References: <OF8AC5B644.037E523E-ON86256BDE.00506DD2@rchland.ibm.com> <152120904000.20020620222650@mysql.com> <20020620194340.GA1772@celeron.dekkers>

> IMHO it is just wasting time on your part, your patches to
> linuxthreads are so trivial that glibc should do the thing you need by
> default.

This has come up before, there is no general agreement on this; I
strongly disagree.

I much prefer to have reasonably large thread stack sizes by default,
rather than being able to create ridicoulous amounts (>1000) of
threads (which, if _required_ by the application, I count as a severe
application bug).

Regards,
Wolfram.

Follow-Ups:
- Re[2]: DLOPEN and Statically linked executable
  - From: Peter Zaitsev
- Re: DLOPEN and Statically linked executable
  - From: Jeroen Dekkers

References:
- Re: DLOPEN and Statically linked executable
  - From: Steve Munroe
- Re[2]: DLOPEN and Statically linked executable
  - From: Peter Zaitsev
- Re: DLOPEN and Statically linked executable
  - From: Jeroen Dekkers

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