Changes between Version 27 and Version 28 of AppDebug

Timestamp:

May 1, 2014, 11:10:51 AM (11 years ago)

Author:

davea

Comment:

--

AppDebug

@@ -19 +19 @@
 you can test it under the BOINC client, but without a project server.
 This will exercise the various forms of interaction with the client.
-If you already have a working project, skip to the next section.
 
 This example assumes that your executable name is '''test.exe''',
@@ -28 +27 @@
  * Put the file
    [http://boinc.berkeley.edu/gitweb/?p=boinc-v2.git;a=blob_plain;f=samples/client_state_save.xml;hb=HEAD samples/client_state_save.xml]
-   in it (modify this file as needed).
+   in it.
+   Modify this file as needed to reflect the input and output files of your application
+   (add '''<file_info>''' and '''<file_ref>''' elements).
  * Create a file '''account_test.xml''' containing
 {{{
@@ -51 +52 @@
 }}}
  (or do the equivalent on Windows).
-
-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.
+
+The client will run your app and then sleep.
+When the job is done,
+check '''projects/test.test/output.txt''' to verify that it worked.
+Your app's stderr output will be somewhere in client_state.xml.
 
 If your app isn't working, there are two ways to debug it.
@@ -142 +144 @@
 For details see [MacBacktrace Mac Backtrace].
 Although that page is written primarily for the Mac, much of it can be used on Linux and UNIX systems as well.
+