.49: get fatal error every time I start it but vs2008 debugger works

[Joseph Stateson]

.47 installed and ran just fine.  .48 installed but will not run unless I used MSVC debugger to continue past the breaks.

Vista 64 with all patches and updates, quad cpu.

This shows up on every execution



I then select vs2008 debug



then position the address register to the xor to allow a return to the caller.  I suspect that the XOR is used to return an OK (eventually) to the caller.  However, it has to be done twice.



have to do the above twice, didnt bother taking a snapshot the 2nd time.  ie: position the cursor at the XOR and then click on "Set Next Statement"



finally shows up and runs ok.

If I qut the program then the same problem occures the next time I run it.
I have DEP turned on for only essential Windows programs and services ie:  boinctasks64.exe is not guarded by DEP.  It is also 64 bit so cannot be under DEP in any event.


From Vista64 event logger

Log Name:      Application
Source:        Application Error
Date:          4/12/2010 11:04:28 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      jstateson2Quad
Description:
Faulting application boinctasks64.exe, version 0.4.9.0, time stamp 0x4bc25a82, faulting module boinctasks64.exe, version 0.4.9.0, time stamp 0x4bc25a82, exception code 0xc0000005, fault offset 0x0000000000092c3f, process id 0x1720, application start time 0x01cadabe69b7e020.

[fred]

0.49 has a serious bug, on my own computer it works ok all the time except at boot-up.
A pointer is accessed before it's initialized, it is set to NULL though  and for some reason it works most of the time.
Most of my testing is done with the debugger... and some errors simply don't show up. Should be easy to correct.