By optimizer, I mean the optimizing part of the compiler. ----- Rom
-----Original Message----- From: Rom Walton Sent: Monday, December 05, 2011 10:51 AM To: 'Raistmer'; David Anderson (BOINC); [email protected] Subject: RE: [boinc_dev] BOINC's initialisation leads to exception Did you build this as a debug build? Or a release build? That callstack only makes since if the optimizer has totally mucked things up. ----- Rom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Raistmer Sent: Sunday, December 04, 2011 4:48 PM To: David Anderson (BOINC); [email protected] Subject: Re: [boinc_dev] BOINC's initialisation leads to exception Call stack is: > ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::_Iterator_base_aux::_Getmycon > t() Line 458 + 0x6 bytes C++ ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::_Vector_const_iterator<_BOINC_T HREADLISTENTRY *,std::allocator<_BOINC_THREADLISTENTRY *> >::operator+=() + 0x34 bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::_Vector_iterator<_BOINC_MESSAGE MONITORENTRY *,std::allocator<_BOINC_MESSAGEMONITORENTRY *> >::operator+=() + 0x13 bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::_Vector_iterator<_BOINC_MESSAGE MONITORENTRY *,std::allocator<_BOINC_MESSAGEMONITORENTRY *> >::operator+() + 0x23 bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::vector<_BOINC_THREADLISTENTRY *,std::allocator<_BOINC_THREADLISTENTRY *> >::insert() + 0x6d bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!std::vector<_BOINC_MESSAGEMONITORENT RY *,std::allocator<_BOINC_MESSAGEMONITORENTRY *> >::push_back() + 0x6c bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!_diagnostics_set_thread_exempt_suspe nd() + 0xb2 bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!_diagnostics_unhandled_exception_mon itor@4() + 0x34 bytes ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!_callthreadstartex() Line 348 + 0x6 bytes C ap_5.06_win_x86_SSE2_OpenCL_ATI.exe!_threadstartex(void * ptd=0x01827690) Line 326 + 0x5 bytes C kernel32.dll!75d5d0e9() [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll] ntdll.dll!775019bb() ntdll.dll!7750198e() ----- Original Message ----- From: David Anderson To: [email protected] Sent: Sunday, December 04, 2011 10:10 PM Subject: Re: [boinc_dev] BOINC's initialisation leads to exception Please send the complete call stack. -- David On 04-Dec-2011 4:34 AM, Raistmer wrote: > Unhandled exception at 0x00401056 in ap_5.06_win_x86_SSE2_OpenCL_ATI.exe: > 0xC0000005: Access violation reading location 0x01010101. > > Place of failure: > > const _Container_base_aux * _Getmycont() const { // Go through the aux > object to get the container return _Myaux ? _Myaux->_Getcont() : 0; } > > > In application it's BOINC's API call: > > retval = boinc_init(); > > Suggested earlier app rebuild didn't help. This BOINC's API failure > hinders accomodation to new project science app version. What can be > done to fix it ? > > App linked vs trunk's rev 23996. > > _______________________________________________ boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To > unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
