[Gc] Thread and Win32
hans.boehm at hp.com
Tue Mar 28 16:07:56 PST 2006
I don't think this ever got answered. I suspect there is no good reason
for this, and both calls should be intercepted. I'd be inclined not to
touch this in the 6.X collectors, but a patch against 7.0alpha would
eventually be welcome, though I'm currently still actively debugging the
Windows port there.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of jim marshall
> Sent: Monday, March 20, 2006 10:33 AM
> To: gc at napali.hpl.hp.com
> Subject: [Gc] Thread and Win32
> This is just a question, I am not having any specific problems....
> I've been doing Linux/Unix programming for about 5+ years
> now, previously I did Windows programming. We are now porting
> our application (which uses the GC) to Windows (what fun -
> since we had no plans to do this). I noticed in the Win32
> readme, for the GC, a note stating that the Win32
> "CreateThread" API is used to start new threads, and also
> found it being called in the source code. While I am not
> noticing any problems (our port is working fine on Windows,
> and I presume most peoples ports work fine with the GC), I am
> curious as to why _beginThread or _beginThreadEx is not being
> used on Win32?
> Specifically I have read (for example:
> https://www.microsoft.com/msj/0797/multithreading.aspx) that
> any program that utilizes the C RunTime should use the
> _beginThread* api's so that the CRT can initialize any
> TLS/TSD it uses.
> Since no one seems to be running into a problem, it is
> probably not a real issue. I just thought I would ask.
> Jim Marshall
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc