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 | It is also of course possible to use a debugger such as {{{gdb}}} with freeDiameter, although its multithreaded design makes it a bit more difficult. |
| 14 | |
| 15 | == Reporting a problem == |
| 16 | |
| 17 | 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. |
| 18 | |
| 19 | 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. |