Unhandled Exception Detected...


log in

Advanced search

Message boards : Number crunching : Unhandled Exception Detected...

Author Message
Silesius
Send message
Joined: 3 Mar 12
Posts: 5
Credit: 591,247
RAC: 2
United States
Message 1317193 - Posted: 19 Dec 2012, 17:20:50 UTC

Just curious about what does the below error mean and whether errors like that (Unhandled Exceptions) are being looked into by seti developers.


<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce GTX 550 Ti
totalGlobalMem = 2147155968
sharedMemPerBlock = 49152
regsPerBlock = 32768
warpSize = 32
memPitch = 2147483647
maxThreadsPerBlock = 1024
clockRate = 1800000
totalConstMem = 65536
major = 2
minor = 1
textureAlignment = 512
deviceOverlap = 1
multiProcessorCount = 4
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 550 Ti is okay
SETI@home using CUDA accelerated device GeForce GTX 550 Ti
setiathome_enhanced 6.09 Visual Studio/Microsoft C++
libboinc: 6.3.22

Work Unit Info:
...............
WU true angle range is : 5.989563
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_GetPowerSpectrum 0.00021 0.00000
v_ChirpData 0.01867 0.00000
v_Transpose4 0.00493 0.00000
FPU opt folding 0.00117 0.00000
SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: d:/Projects/SETI/seti_boinc/client/cuda/cudaAcc_pulsefind.cu
Line: 236



Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x75C24906

Engaging BOINC Windows Runtime Debugger...


</stderr_txt>
]]>

Profile ivan
Volunteer tester
Avatar
Send message
Joined: 5 Mar 01
Posts: 625
Credit: 143,569,933
RAC: 150,239
United Kingdom
Message 1317244 - Posted: 19 Dec 2012, 18:32:16 UTC - in response to Message 1317193.

Just curious about what does the below error mean and whether errors like that (Unhandled Exceptions) are being looked into by seti developers.


It looks to me like this
<message>
Maximum elapsed time exceeded
</message>

threw the exception that caused this

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x75C24906

Engaging BOINC Windows Runtime Debugger...

There's probably no other way to handle maxtime as there's always the possibility it's an infinite loop and the programme will never return to a call-back.
____________

Josef W. SegurProject donor
Volunteer developer
Volunteer tester
Send message
Joined: 30 Oct 99
Posts: 4305
Credit: 1,074,055
RAC: 1,205
United States
Message 1317377 - Posted: 19 Dec 2012, 23:10:13 UTC - in response to Message 1317193.

Just curious about what does the below error mean and whether errors like that (Unhandled Exceptions) are being looked into by seti developers.
...
SETI@home error -12 Unknown error
cudaAcc_find_triplets erroneously found a triplet twice in find_triplets_kernel
File: d:/Projects/SETI/seti_boinc/client/cuda/cudaAcc_pulsefind.cu
Line: 236



Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x75C24906

Engaging BOINC Windows Runtime Debugger
...

When the code was ported to CUDA, they had to make some choices about how much video RAM to set aside for capturing signals while processing many arrays in parallel. They decided that multiple triplets in one array were rare enough to simply handle that case by throwing an exception, which in the SETI code is defined as "Unsupported function". BOINC doesn't know that application-specific code so calls it "unknown".

In short, those -12 errors are an indication of a data pattern which occurs rarely, though not quite as rarely as had been hoped. There's another form which indicates "cudaAcc_find_triplets doesn't support more than MAX_TRIPLETS_ABOVE_THRESHOLD numBinsAboveThreshold in find_triplets_kernel" which is just another even more rare data pattern.

The "Breakpoint Encountered" part is because the BOINC API forces a breakpoint hoping to capture more information about the unhandled exception.
Joe

Message boards : Number crunching : Unhandled Exception Detected...

Copyright © 2014 University of California