Changes between Version 3 and Version 4 of AppDebug


Ignore:
Timestamp:
May 29, 2007, 2:56:54 PM (17 years ago)
Author:
Nicolas
Comment:

Typo (wrong word?) fix, and some formatting

Legend:

Unmodified
Added
Removed
Modified

  • AppDebug

    v3 v4  
    2626If you haven't set up your workunit and result template files correctly,
    2727or if there's a problem with your application version file setup,
    28 this can be debugging by running the client with the --exit_before_start
    29 or --exit_after_finish command-line options.
     28this can be debugged by running the client with the `--exit_before_start`
     29or `--exit_after_finish` command-line options.
    3030
    3131== Getting and deciphering stack traces ==
    32 Once your application is working on your own computers, you're ready to test it with outside computers (alpha testers initially). It may crash on some computers, e.g. because their software or hardware is different from yours. You'll get some information back in the stderr_txt field of the results. If your application called boinc_init_diagnostics() with the BOINC_DIAG_DUMPCALLSTACKENABLED flag set, and you included symbols, hopefully you'll get symbolic stack traces.
     32Once your application is working on your own computers, you're ready to test it with outside computers (alpha testers initially). It may crash on some computers, e.g. because their software or hardware is different from yours. You'll get some information back in the stderr_txt field of the results. If your application called `boinc_init_diagnostics()` with the `BOINC_DIAG_DUMPCALLSTACKENABLED` flag set, and you included symbols, hopefully you'll get symbolic stack traces.
    3333
    3434To decipher a Windows stack trace go [AppDebugWin here].