Search results

There are three different projects that can be built as Debug or Release versions, for both MSVC 6 and VS.Net: : Debug: ptlibsd.lib Release: ptlibs.lib

; printmsg: boolean: Print sent/received frames to output if the module's debug

Logging of spandsp messages at DEBUG and FLOW levels is disabled by default. It can be controlled at runtime fro * ''debug spandsp'' - to show the current detailed logging status

; printxml: boolean/string: Print sent/received XML data to output if debug

* parameters for debugging ; printxml: boolean/string: Print sent/received XML data to output if debug

; print_attributes: bool: Print returned attributes on debug level ALL

* [[Debug Output]] [[Category:Debug]] [[Category:Telnet]] [[Category:Rmanager]] [[Category:External]] [[Categor

;for debugging yate debug on

* [[Debug_Output#Debugging_levels|Debug levels]]

...o change all the other modules that are dependent, and also because we can debug what's happening much easier since we know which module passes which data t Debug(DebugInfo,"Route for driver %s",driver);

* Showing debug output

placing a call to 1001 you should also see some more debug messages from pbx.py.

** Echo a message for debug purpose.

*to run in debug mode: -v Verbose debugging (you can use more than once)

* Use '''Yate::Debug''' to send debugging output to console or log file, this can be turned on or off by providin

raise debug level (debug on) and you should be able to see timer messages.

=== Debugging mutex issues=== Debugging multithreaded programs is a difficult task since usually the problems o

==Debugging == * [[Debugging in Yate]]

* '''debug''' will compile the binaries with debugging information make -s debug

# override DEBUG at compile time to enable full debug or remove it all DEBUG :=