Navigation

Changes between Version 2 and Version 3 of Troubleshooting


Ignore:
Timestamp:
Mar 1, 2011, 11:26:36 AM (13 years ago)
Author:
Sebastien Decugis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Troubleshooting

    v2 v3  
    77
    88If your problem occurs following a reproductible sequence of events, you may get useful information by:
    9  * Compiling the framework with DEBUG support. This is done by selecting for example CMAKE_BUILD_TYPE=Debug during the build configuration (see [wiki:Installation#cmakeflags] for more information).
    10  * Running the daemon with a higher level of details in the debug output. This is done by passing one or more {{{-d}}} flags on the command line. The level can be increased up to 10 times ({{{-dddddddddd}}}) but the framework becomes usually unusable after 4 or 5... Anyway, in most cases, {{{-ddd}}} should give enough feedback to get a precise idea of what is going on.
     9 * Compiling the framework with DEBUG support.
     10   This is done by selecting for example CMAKE_BUILD_TYPE=Debug
     11   during the build configuration
     12   (see [wiki:Installation#cmakeflags] for more information).
     13
     14 * Running the daemon with a higher level of details in the debug output.
     15   Default is level 1 : INFO.
     16   The level is increased by passing one or more {{{-d}}} flags on the command line.
     17   In most cases, {{{-ddd}}} should give enough feedback to get a precise
     18   idea of what is going on.
     19   The levels are defined in [source:freeDiameter/include/freeDiameter/libfdproto.h libfdproto.h] as follow:
     20   * NONE (0) : No message is displayed.
     21   * INFO (1) : Only important messages and errors are shown.
     22     This is the default, but might be overwritten at compilation.
     23   * FULL (2) : Additional information, allowing to follow the execution.
     24   * ANNOYING (4) : Very verbose level, including for example loops contents.
     25   * FCTS (6) : Traces entry in most functions, with their parameters.
     26   * CALL (9) : Traces almost all function calls.
     27
     28   The levels above 3 will result in a lot of information being displayed,
     29   and a slowing of the daemon's execution. These must be used with care.
     30   To get level 3 for example (assuming default is 1), use:
     31{{{
     32$ freeDiameterd -dd
     33}}}
     34
    1135 * In addition, if you were able to isolate the function or at least source file where the problem is occurring, you can use {{{--dbg_func=<funcname>}}} or {{{--dbg_file=<filename>}}} to get maximum detailed information in this function/file only.
    1236