#### 2.3.2 Detailed log file ¶

DejaGnu also saves a detailed log file (`.log`), showing any output generated by test cases as well as the summary output. For example, after running `runtest --tool binutils`, a detailed log file will be written to `binutils.log`. Normally, DejaGnu writes this file in your current working directory. Use the `--outdir` option to select a different output directory.

Sample detailed log for g++ tests

    Test Run By bje on Sat Nov 14 21:07:23 AEDT 2015

                    === g++ tests ===

    Running ./g++.other/t01-1.exp ...
    PASS:   operate delete

    Running ./g++.other/t01-2.exp ...
    FAIL:   i960 bug EOF
    p0000646.C: In function `int  warn_return_1 ()':
    p0000646.C:109: warning: control reaches end of non-void function
    p0000646.C: In function `int  warn_return_arg (int)':
    p0000646.C:117: warning: control reaches end of non-void function
    p0000646.C: In function `int  warn_return_sum (int, int)':
    p0000646.C:125: warning: control reaches end of non-void function
    p0000646.C: In function `struct foo warn_return_foo ()':
    p0000646.C:132: warning: control reaches end of non-void function
    Running ./g++.other/t01-4.exp ...
    FAIL:   abort
    900403_04.C:8: zero width for bit-field `foo'
    Running ./g++.other/t01-3.exp ...
    FAIL:   segment violation
    900519_12.C:9: parse error before `;'
    900519_12.C:12: Segmentation violation
    /usr/latest/bin/gcc: Internal compiler error: program cc1plus got fatal signal

                    === g++ Summary ===

    # of expected passes            1
    # of expected failures          3
    /usr/latest/bin/g++ version cygnus-2.0.1