This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Problem with stack size in pthreads
- To: Ulrich Drepper <drepper at cygnus dot com>
- Subject: Re: Problem with stack size in pthreads
- From: Kaz Kylheku <kaz at ashi dot footprints dot net>
- Date: Thu, 12 Jul 2001 13:42:19 -0700 (PDT)
- cc: Andreas Jaeger <aj at suse dot de>, <libc-alpha at sources dot redhat dot com>, <Hui dot Huang at sum dot com>
On 12 Jul 2001, Ulrich Drepper wrote:
> Date: 12 Jul 2001 13:15:14 -0700
> From: Ulrich Drepper <drepper@redhat.com>
> Reply-To: Ulrich Drepper <drepper@cygnus.com>
> To: Kaz Kylheku <kaz@ashi.footprints.net>
> Cc: Andreas Jaeger <aj@suse.de>, libc-alpha@sources.redhat.com,
> Hui.Huang@sum.com
> Subject: Re: Problem with stack size in pthreads
>
> Kaz Kylheku <kaz@ashi.footprints.net> writes:
>
> > How about making checks for a stack pointer that is getting too
> > close to __pthread_initial_thread_bos and then adjusting the value.
> > This should be okay unless the pointer leaps by a huge amount, going from
> > not-too-close to too-far in one step, or in multiple activations without
> > any intermittent calls to thread_self.
>
> Nothing which only works in some situations is even worth thinking
> about. It just gives a wrong sense of security.
I don't like it either for the same reason. Leave it to the developers
of LIBCMT.DLL. ;) Did you read the second idea?