No resources that I can see. Even if that was the problem, I don't think it would cause the breakpoint in Run() to not be able to be set.
Here's more info I just noticed. When the thread exits I get this in the debug pane: The thread 0x112 has exited with code -842150451 (0xCDCDCDCD). This (0xCDCDCDCD) means that something was allocated on the heap but not initialized. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Phil Daley > Sent: Friday, October 29, 2004 9:39 AM > To: [EMAIL PROTECTED] > Subject: Re: [msvc] thread exits prematurely > > > At 10/29/2004 09:32 AM, Palmer, Jean L. wrote: > > >The thread starts, and goes through its InitInstance() > function. Then it > >immediately goes to ExitInstance() and its destructor. I > can't figure out > >why it immediately goes to ExitInstance() and quits, > instead of running. > >The call stack when it enters ExitInstance() is: > > Does your thread have any resources that it uses? > > Sometimes programs exit unexplainably when they try to access an > unavailable resource, like a string. _______________________________________________ msvc mailing list [EMAIL PROTECTED] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
