| | 1 | [[PageOutline(2-4)]] |
| | 2 | = Troubleshooting = |
| | 3 | |
| | 4 | This page describes a few steps that you can follow in order to track a problem with {{{freeDiameter}}}. |
| | 5 | |
| | 6 | == Gathering debug messages == |
| | 7 | |
| | 8 | If 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. |
| | 11 | |
| | 12 | 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. |
| | 13 | |
| | 14 | ---- |
