public inbox for
 help / color / mirror / Atom feed
* pthread_self inside thread procedure
@ 2004-11-19  2:09 Will Bryant
  0 siblings, 0 replies; only message in thread
From: Will Bryant @ 2004-11-19  2:09 UTC (permalink / raw)
  To: pthreads-win32

Hi all,

With the new release, I'm finding that my threads can't detach; at the 
very start of the thread procedure, they do a 

This call is returning ESRCH, because while pthread_self() is returning 
a valid pthread_t structure, the first element of it is always NULL (the 
second member is consistently a fairly high number, eg. 2312903, but 
that may not have any significance).

So, unless I'm missing something, it seems that pthread_self() is broken 
with the new release.  Can others reproduce this problem?

Best regards,

Will Bryant
Systems Architect, eCOSM.
Phone +64 3 365 4176 | Mobile +64 21 655 443

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-11-19  2:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-11-19  2:09 pthread_self inside thread procedure Will Bryant

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