Change per-file debug and verbose levels to be per-module, the way

users expect them to work.

'core set debug' and 'core set verbose' can optionally change the
level for a specific filename; however, this is actually for a
specific source file name, not the module that source file is included
in. With examples like chan_sip, chan_iax2, chan_misdn and others
consisting of multiple source files, this will not lead to the
behavior that users expect. If they want to set the debug level for
chan_sip, they want it set for all of chan_sip, and not to have to
also set it for reqresp_parser and other files that comprise the
chan_sip module.

This patch changes this functionality to be module-name based instead
of file-name based.

To make this work, some Makefile modifications were required to ensure
that the AST_MODULE definition is present in each object file produced
for each module as well.

Review: https://reviewboard.asterisk.org/r/574/



git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@253917 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Kevin P. Fleming
2010-03-23 14:22:27 +00:00
parent f9e4d024c9
commit ae6008ef3a
10 changed files with 115 additions and 84 deletions

11
CHANGES
View File

@@ -426,6 +426,17 @@ Miscellaneous
* chan_dahdi now supports reporting alarms over AMI either by channel or span via
the reportalarms config option.
CLI Changes
-----------
* The 'core set debug' and 'core set verbose' commands, in previous versions, could
optionally accept a filename, to apply the setting only to the code generated from
that source file when Asterisk was built. However, there are some modules in Asterisk
that are composed of multiple source files, so this did not result in the behavior
that users expected. In this version, 'core set debug' and 'core set verbose'
can optionally accept *module* names instead (with or without the .so extension),
which applies the setting to the entire module specified, regardless of which source
files it was built from.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 1.6.1 to Asterisk 1.6.2 -------------
------------------------------------------------------------------------------