Changes between Version 4 and Version 5 of Troubleshooting

Timestamp:

Mar 3, 2011, 5:12:28 PM (13 years ago)

Author:

Administrator

Comment:

--

Troubleshooting

@@ -2 +2 @@
 = Troubleshooting =
 
-This page describes a few steps that you can follow in order to track a problem with {{{freeDiameter}}}.
+This page describes a few steps that you can follow in order to better understand a problem you are encountering with {{{freeDiameter}}}.
 
 == Gathering debug messages ==
@@ -8 +8 @@
 If your problem occurs following a reproductible sequence of events, you may get useful information by:
  * Compiling the framework with DEBUG support. 
-   This is done by selecting for example CMAKE_BUILD_TYPE=Debug 
-   during the build configuration 
+   This is done by building freeDiameter with CMAKE_BUILD_TYPE=Debug option
    (see [wiki:Installation#cmakeflags] for more information).
 
@@ -15 +14 @@
    Default is level 1 : INFO. 
    The level is increased by passing one or more {{{-d}}} flags on the command line. 
-   In most cases, {{{-ddd}}} should give enough feedback to get a precise 
+   In many cases, {{{-dd}}} or {{{-ddd}}} should give enough feedback to get a precise 
    idea of what is going on.
    The levels are defined in [source:freeDiameter/include/freeDiameter/libfdproto.h libfdproto.h] as follow:
@@ -23 +22 @@
    * FULL (2) : Additional information, allowing to follow the execution.
    * ANNOYING (4) : Very verbose level, including for example loops contents.
-   * FCTS (6) : Traces entry in most functions, with their parameters.
+   * FCTS (6) : Traces entry inside most framework functions, with their parameters.
    * CALL (9) : Traces almost all function calls.
 
    The levels above 3 will result in a lot of information being displayed, 
-   and a slowing of the daemon's execution. These must be used with care. 
+   and a slowing of the framework's execution. These must be used with care. 
    To get level 3 for example (assuming default is 1), use:
 {{{
+#!sh
 $ freeDiameterd -dd
 }}}
@@ -39 +39 @@
 == Reporting a problem ==
 
-Please use the help function of this site first to look for similar reports. This searches both the existing tickets and the mailing-list archives.
+Please use the "Search" function of this site first to look for similar reports. This searches both the existing tickets and the mailing-list archives.
 
-If your problem is not already solved, please report to the support mailing-list: help@freediameter.net. If possible, include as much useful information as possible, including: your configuration file (if relevant, strip / alter any confidential information), the debug messages showing the problem, the Operating System on which you are running the framework, the steps to reproduce the problem. In some cases, a network capture (realized with ''wireshark'' for example) may also be helpful.
+If your problem is not already solved, please report to the support mailing-list: help@freediameter.net. If possible, include as much useful information as possible, including: 
+ * your configuration file -- if relevant, strip / alter any confidential information
+ * the debug messages showing the problem
+ * the Operating System on which you are running the framework
+ * the steps to reproduce the problem. 
+In some cases, a network capture (realized with ''wireshark'' for example) may also be helpful.
 
 ----