Re: AfxBeginThread failure - how to find cause?

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 13 Mar 2007 19:12:16 -0700

Message-ID:

<uLq4y4dZHHA.4772@TK2MSFTNGP05.phx.gbl>

GetLastError after AfxBeginThread isn't likely to give you CreateThread
error code.

"AliR (VC++ MVP)" <AliR@online.nospam> wrote in message
news:GvDJh.3021$Qw.492@newssvr29.news.prodigy.net...

Did you try GetLastError after the call to AfxBeginThread.

Honestly I have never had AfxBeginThread fail on me.

AliR.

"UI Guy" <sherwood@programmer.net> wrote in message
news:1173771030.829819.323170@v33g2000cwv.googlegroups.com...

In an MFC pgm under VS2005sp1, I am creating a worker thread using
AfxBeginThread. Under certain circumstances which I can't quite pin
down, AfxBeginThread returns NULL, indicating it has failed. Is there
any way I can find out the cause of the failure, such as an error
code? I have tried tracing through the code with the debugger, but
what is apparently detecting the error condition is in MS code for
which I don't have the source.

My specific code is

CWinThread* pThread=AfxBeginThread(MyControlFunction,&ti,0/*priority*/,
230000000/*stack size*/);

and a test for pThread==NULL immediately following. It is a rather
large stack size.

The thread terminates by returning from MyControlFunction.

Usually creation of the worker thread succeeds the first time, and
fails the second. There seems to be some interaction between failure
and use of the file open common dialog in some preceding code.