This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
pthread_attr_setstackaddr bug?
- To: glibc-linux at ricardo dot ecn dot wfu dot edu
- Subject: pthread_attr_setstackaddr bug?
- From: kd at flaga dot is
- Date: Tue, 14 Dec 1999 16:20:56 +0000
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
Hi,
Shouldn't the implementation of pthread_attr_setstackaddr funxction be
closer too
attr->__stackaddr = stackaddr;
if(stackaddr != NULL)
{
attr->__stackaddr_set = 1;
}
else
{
attr->__stackaddr_set = 0;
}
return 0;
If the old implementation is used then calling pthread_attr_setstackaddr
(in attr.c) with NULL argument causes
pthread_allocate_stack() (in manager.c) to think that we have a user
supplied stack because only __stackaddr_set is
checked there not the actual stackaddress?
K.D.