Changes between Version 23 and Version 24 of AppDebug

Timestamp:

Sep 7, 2011, 4:56:19 PM (14 years ago)

Author:

davea

Comment:

--

AppDebug

@@ -52 +52 @@
  (or do the equivalent on Windows).
 
-The client should run your app and then sleep.
+The client will run your app and then sleep.
 Check '''projects/test.test/output.txt''' to verify that it worked.
-
+Your app's stderr output will be somewhere in client_state.xml.
 You can run the BOINC Manager after running the client,
 and verify that its various functions
 (fraction done reporting, elapsed time reporting, suspend/resume, etc.)
 are working.
+
+If your app isn't working,
+there are two ways to debug it.
+First, if you put
+{{{
+<exit_before_start/>
+}}}
+in the config options,
+the BOINC client will set up the "slot directory" (usually slots/0/)
+where your application will run, and then exit.
+You can cd into that directory,
+check that the needed files are there,
+and run the app manually (perhaps under a debugger) by typing
+{{{
+../../projects/test.test/test.exe
+}}}
+In this approach the app runs in standalone mode, since the BOINC client is not running.
+When it's done, its output files and stderr output file will be in the slot directory.
+
+The second approach is to put
+{{{
+<run_apps_manually/>
+}}}
+in the config options.
+If you do this, the BOINC client will set up to run your app,
+but won't actually run it; you must run it manually as above.
+In this case your app will interact with the BOINC client
+(suspend/resume, fraction-done reporting, etc.).
+When it's done, the output files will be in the project directory
+and the stderr output in client_state.xml
 
 == Testing with a BOINC client and project ==