formal debug levels

The debug sections have been formalized. But as yet there does not appear
to be any consensus on what any given level should contain. Simply a "is
it too much" guess.

I propose that we give each level a broad category description and use
that as a guide when deciding where to place any given debugs() detail.

Just off the top of my head I have these in rough priority order:

 (0) serious WARNINGS and errors.
 (1) gross component start/stop info

 - component API calls

 - per- function/method start-stop info
   (for all those "xyz: Started.", "returns with V" bits)

 - control path info
   (whether any given code path has occured, possibly why).

 - SMALl local data / state data
   (variables content)

 - LARGE local data / state data
   (buffer content)

Anything else?

Secondly;
  since bug #2083 I have wondered about the usefulness of a macro/function
that could be used in the section part of debugs() and caused display if
any of N sections passed to it were at the right level.

  ie debugs(SECT(42,83),9, "Hi"); // display in EITHER (42 or 83) level 9

Amos
Received on Tue Oct 23 2007 - 21:51:00 MDT