Browse code

modules/debugger: refresh README

Victor Seva authored on 17/05/2013 15:49:14
Showing 1 changed files
... ...
@@ -10,7 +10,7 @@ Daniel-Constantin Mierla
10 10
 
11 11
    <miconda@gmail.com>
12 12
 
13
-   Copyright � 2010 Daniel-Constantin Mierla (asipto.com)
13
+   Copyright (c) 2010 Daniel-Constantin Mierla (asipto.com)
14 14
      __________________________________________________________________
15 15
 
16 16
    Table of Contents
... ...
@@ -45,6 +45,7 @@ Daniel-Constantin Mierla
45 45
               5.1. dbg.ls
46 46
               5.2. dbg.trace
47 47
               5.3. dbg.bp
48
+              5.4. dbg.mod_level
48 49
 
49 50
         6. Usage
50 51
 
... ...
@@ -94,6 +95,7 @@ Chapter 1. Admin Guide
94 94
         5.1. dbg.ls
95 95
         5.2. dbg.trace
96 96
         5.3. dbg.bp
97
+        5.4. dbg.mod_level
97 98
 
98 99
    6. Usage
99 100
 
... ...
@@ -295,6 +297,7 @@ if($si=="10.0.0.10")
295 295
    5.1. dbg.ls
296 296
    5.2. dbg.trace
297 297
    5.3. dbg.bp
298
+   5.4. dbg.mod_level
298 299
 
299 300
 5.1. dbg.ls
300 301
 
... ...
@@ -365,6 +368,20 @@ if($si=="10.0.0.10")
365 365
                 dbg.bp eval 1234 $fu
366 366
                 dbg.bp move 1234
367 367
 
368
+5.4. dbg.mod_level
369
+
370
+   Specify module log level.
371
+
372
+   Name: dbg.mod_level
373
+
374
+   Parameters:
375
+     * _module_ : For core log level, use module name 'core'
376
+     * _level_ : integer
377
+
378
+   Examples of use with kamcmd:
379
+                dbg.mod_level core 3
380
+                dbg.mod_level tm 3
381
+
368 382
 6. Usage
369 383
 
370 384
    A common usage is to investigate the execution path for a specific SIP