[asterisk-bugs] [Asterisk 0017159]: [patch] HowTo: Collecting Debug Information

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17159 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17159
Category:                   Documentation
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-09 12:20 CDT
Last Modified:              2010-04-10 07:26 CDT
====================================================================== 
Summary:                    [patch] HowTo: Collecting Debug Information
Description: 
In an effort to help reporters and developers work together, I have created
a HowTo document to help collect debug information. This will help people
reporting an issue collect useful information for a developer.
====================================================================== 

---------------------------------------------------------------------- 
 (0120245) tzafrir (manager) - 2010-04-10 07:26
 https://issues.asterisk.org/view.php?id=17159#c120245 
---------------------------------------------------------------------- 
a. Maximal verbosity and debug levels:

$ grep -h -o 'ast_verb([^,]*,' */*.c | sort | uniq -c
    126 ast_verb(0,
    136 ast_verb(1,
      2 ast_verb(10,
      6 ast_verb(11,
    122 ast_verb(2,
    498 ast_verb(3,
     64 ast_verb(4,
      7 ast_verb(6,
      1 ast_verb(level,

"level" is from res_agi, where it comes from the user. 
10 and 11 seem at first glance to be ones that may be safely changed to be
5 or so.

For ast_debug we get:

grep -h -o 'ast_debug([^,]*,' */*.c | sort | uniq -c
      9 ast_debug(0,
   1513 ast_debug(1,
      4 ast_debug(10,
      1 ast_debug(1000,
    171 ast_debug(2,
    243 ast_debug(3,
    132 ast_debug(4,
     37 ast_debug(5,

Likewise, I suspect that the 4 "10"-s and the single "1000" could be
safely changed to lower values.

Often the driver-level traces (sip debug, iax2 debug, pri set debug, and
such) are confusing.

Another thing to note is that as of asterisk 1.6.<I'm not sure, exactly>,
you can set debug specifically on source files. In trunk this has been made
possible to use per module. Thus it may be nicer to disable most debugs,
but still have debugging enabled on some files. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-10 07:26 tzafrir        Note Added: 0120245                          
======================================================================