| log in |
|
1)
Message boards :
Number crunching :
wrapper source code
(Message 5263)
Posted 7 Jun 2019 by Ken_g6 Any chance the wrapper could be compiled from a newer version? Like this one? https://github.com/ibethune/llr_wrapper/blob/master/wrapper.C Most likely the wrapper would have to be modified, but still that code has a lot of benefits the wrapper here doesn't. |
|
2)
Message boards :
Number crunching :
Invalid WUs that aren't invalid
(Message 5261)
Posted 7 Jun 2019 by Ken_g6 Alright, how about fixing it in the wrapper? If the number of SIGSEGV's in stderr.txt is greater than the number of RESTARTs, restart LLR (delete the z-file) and write "RESTARTing" lines until the number of SIGSEGV's in stderr.txt equals the number of RESTARTs. Edit: Or, more simply, just abort the WU when there's a SIGSEGV in stderr.txt. Why are you using a different wrapper than PrimeGrid, anyway? (Doing the above would be a reason, but not a reason for not including a lot of features from said wrapper.) |
|
3)
Message boards :
Number crunching :
Invalid WUs that aren't invalid
(Message 5259)
Posted 7 Jun 2019 by Ken_g6 Here's a stderr: 01:52:08 (4058): wrapper (7.2.26012): starting
01:52:08 (4058): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
12:12:26 (2180): wrapper (7.2.26012): starting
12:12:26 (2180): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
SIGSEGV: segmentation violation
Stack trace (11 frames):
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu(boinc_catch_signal+0x65)[0x41fa15]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11670)[0x7fbe3ef15670]
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu[0x464351]
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu[0x45f554]
/lib/x86_64-linux-gnu/libc.so.6(+0x357f0)[0x7fbe3eb727f0]
/lib/x86_64-linux-gnu/libc.so.6(nanosleep+0x2d)[0x7fbe3ec0a2ed]
/lib/x86_64-linux-gnu/libc.so.6(usleep+0x34)[0x7fbe3ec3c334]
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu[0x433ca3]
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu[0x407ddd]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fbe3eb5d3f1]
../../projects/srbase.my-firewall.org_sr5/wrapper_26012-v2_x86_64-pc-linux-gnu[0x404f59]
Exiting...
17:00:48 (3539): wrapper (7.2.26012): starting
17:00:48 (3539): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999 -t4)
20:38:46 (3539): llr64 exited; CPU time 50504.952000
20:38:46 (3539): called boinc_finish See, there was a SIGSEGV. I think that happened when the WU was suspended. But then the computation was started over. That time it succeeded. Can you fix this? |