Well 0x80000003 is what error code is returned when an application asserts, which is different than the original error code.
Both of these lines are generated by the C Runtime Library and should be properly filled out by rebuilding the application in the debug configuration. ERROR: Invalid parameter detected in function (null). File: (null) Line: 0? ERROR: Expression: (null)? However if the app did assert and returned 0x80000003 it should have also returned a crash report which should include the call stacks of all the threads which should give you the same information that the two ERROR lines above would give. ----- Rom -----Original Message----- From: Raistmer [mailto:[email protected]] Sent: Sunday, August 01, 2010 3:12 PM To: Raistmer; Rom Walton; [email protected] Subject: Re: [boinc_dev] Incorrect function when running under BOINC Now I advanced further and got error in BOINC function call: Code: // Initialize BOINC // fprintf(stderr,"before boinc_parse_init_data_file\n"); boinc_parse_init_data_file(); fprintf(stderr,"before boinc_get_init_data\n"); STDERR: <![CDATA[ <message> ????????? ?????? ??????????? (0x80000003) - exit code -2147483645 (0x80000003) </message> <stderr_txt> after diagnstic init? before boinc_parse_init_data_file? ERROR: Invalid parameter detected in function (null). File: (null) Line: 0? ERROR: Expression: (null)? What could be wrong there? ----- Original Message ----- From: "Raistmer" <[email protected]> To: "Raistmer" <[email protected]>; "Rom Walton" <[email protected]>; <[email protected]> Sent: Saturday, July 24, 2010 10:31 PM Subject: Re: [boinc_dev] Incorrect function when running under BOINC > Well, i added few fprintfs just after init diagnostics, boinc init call > and so on. > there is nothing in stderr again. Probably it means very first boinc api > call, init diagnostic, failed and caused exit(1) call. Any thoughts why it > could fail? > > ----- Original Message ----- > From: "Raistmer" <[email protected]> > To: "Rom Walton" <[email protected]>; <[email protected]> > Sent: Tuesday, July 20, 2010 12:12 PM > Subject: Re: [boinc_dev] Incorrect function when running under BOINC > > >> Thanks! >> What I found: >> >> 0) >> if (err != CL_SUCCESS) { >> std::cerr << "ERROR: " << name << " (" << err << ")" << >> std::endl; >> exit(1); >> } >> Not th case, no "ERROR" in stderr. >> 1) >> fprintf(stderr, "bad arg: %s\n", argv[i]); >> usage(); >> exit(1); >> Not the case cause no "bad arg" in stderr >> >> 2) >> PowerSpectrum = (float*) calloc_a(NumPointsInChunk, sizeof(float), >> MEM_ALIGN); >> if (PowerSpectrum == NULL) { >> printf("Could not allocate Power Spectrum array in >> v_BaseLineSmooth()\n"); >> exit(1); >> } >> >> can't say if it's what I looking for cause additional output goes to >> stdout >> instead of stderr, need to rebuild to check... >> >> But if it's very place, why buffer allocation fails under BOINC while it >> goes OK w/o it? >> >> ----- Original Message ----- >> From: "Rom Walton" <[email protected]> >> To: "Raistmer" <[email protected]>; <[email protected]> >> Sent: Tuesday, July 20, 2010 11:47 AM >> Subject: RE: [boinc_dev] Incorrect function when running under BOINC >> >> >> Search the source code of the app for exit(1) or exit(EXIT_FAILURE) >> >> ----- Rom >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Raistmer >> Sent: Tuesday, July 20, 2010 3:41 AM >> To: [email protected] >> Subject: [boinc_dev] Incorrect function when running under BOINC >> >> When running offline app works OK, but being launched by BOINC it fails >> with >> "incorrect function exit code 0x1" >> Stderr: >> <stderr_out> >> <![CDATA[ >> <message> >> =ooo?y? ??yu?o . (0x1) - exit code 1 (0x1) >> </message> >> ]]> >> </stderr_out> >> >> No additional info available. >> Maybe there are some known possible reasons of such behavior? Someone >> encountered such situation? >> >> _______________________________________________ >> 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.
