Seti@Home optimized science apps and information
Optimized Seti@Home apps => Windows => Topic started by: Ghost0210 on 01 Jul 2010, 01:15:28 pm
-
Hi All,
Had a query on the NC forum @ Main asking about some firewall warnings a users getting
http://setiathome.berkeley.edu/forum_thread.php?id=60568
Hope someone here could shed some light on why he's getting these messages?
Post from user:
It seems that MB_6.08_CUDA_V12_noKill_FPLim2048.exe is attempting to initiate outgoing connections to 207.46.212.122 (Microsoft Corp) and 128.32.18.189 (isaac.ssl.berkeley.edu).
Thanks
-
Sounds like it's eithier getting -177 errors, or crashed because of a different reason, i beliewe isaac.ssl.berkeley.edu is where the Symbol files for crashes is stored,
(isaac.ssl.berkeley.edu has been under stress because of Seti's -177 storm) and it'll be reporting it's crashed to microsoft too,
Claggy
-
Yup. Boincapi, the 'library bits' compiled into all science applications under the Boinc framework, are wired to trigger an internal 'Boinc Runtime Debugger' when some crash occurs. Checking the stderr.txt output for such a crashed task originating from third party builds will most often look like gibberish because neither Berkeley, nor Microsoft have symbols for those for the debugger mechanism to locate (But it tries anyway).
Berkeley does, I assume, have symbol files in a symbol repository (A windows development thing) for stock applications & Boinc components, and Microsoft certainly has publicly available debug symbols for their windows components etc, so It can be a useful tool for deciphering what's going on in some specific cases .... But more often that not crashes originate in some not directly related driver & such, where symbols usually aren't available.
Either allowing or blocking those requests for debug information (symbol files) doesn't matter to anyone really, so it's a personal choice.
Jason
-
Thanks Jason/Claggy ;D