If present, don't show anything related to computing.
Use this for Bossa/Bolt projects, and the BOINC message boards.
svn path=/trunk/boinc/; revision=15228
the BOINC icon, since the preview window is only 300x200 or
so. We shouldn't launch the data management thread when
launched in preview mode.
clientscr/
screensaver_win.cpp
svn path=/trunk/boinc/; revision=15227
of the option. '-' just causes the CC to exit while
printing its help fr the commandline options.
clientgui/
BOINCClientManager.cpp
svn path=/trunk/boinc/; revision=15214
Old: get_shmem_seg_name() tries names of the form shm_boinc_N
until it finds one for which creating succeeds.
Then it detaches (deletes) the segment and records the name.
Later, the segment is created again.
This creates a race condition if two core clients
are running on the same host.
It's also kind of silly.
New: get_shmem_seg_name() doesn't detach the segment,
and we dont have to create it again later.
svn path=/trunk/boinc/; revision=15172
Keep track of the "easiest" job that has been rejected by EDF sim.
Any jobs harder than this one can be rejected without doing the sim.
svn path=/trunk/boinc/; revision=15171
to avoid confusion with "name" field of CUDA.
This is a bug fix - please port.
- start script: don't error out if run_state.xml file is empty
(which happens if project runs out of disk space)
svn path=/trunk/boinc/; revision=15168
compile time to the module information dumped during a crash.
NOTE: This should give a project admin a tickle that the PDB
and EXE names need to be set before compiling and not renamed
after the fact.
lib/
stackwalker_win.cpp
svn path=/trunk/boinc/; revision=15165
- client: increase <abort> timeout from 5 sec to 60;
this gives the diagnostic system time to download
symbol files (which may be several MB) and write a stack trace.
svn path=/trunk/boinc/; revision=15162
check to make sure that stdout_file and stderr_file are not null before
attempting to close them. If they are null return ERR_FOPEN so that
the next message logged can attempt to cycle the log without error.
- CLIENT: Make sure the diagnostics framework is initialized before
the config file is parsed or the command line is parsed, that way
if and unexpected XML tab or command line parameter is found the
client doesn't crash.
NOTE: The client would only crash if the log file was already greater
than 2MB which would cause the client to attempt to cycle the
log files. Since the diagnostics framework wasn't initialized yet
nothing was logged to the log file, no call stack was generated,
and the default Windows debugging environment was fired up.
client/
main.C
lib/
diagnostics.C
svn path=/trunk/boinc/; revision=15157
David Anderson