Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 9514] New: Better internal debugging for sorcery

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 9514] New: Better internal debugging for sorcery
  • Date: 27 Aug 2006 07:34:45 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=9514

Summary: Better internal debugging for sorcery
Product: Sorcery
Version: Untargetted future release
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Unknown
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: dmlb2000 AT gmail.com


I think it'd be nice to have a better system of debugging than 'all or none'.

Some ideas:
1) debug levels, So from a very high level debug output to a very specific low
level output (set -x for some of it is what I'm thinking)

2) Easy to use filters on the compiled debug log... so we can pick specifics
out
of a potentially very large debug log. I was thinking on prepending some
variables like the following.

<script-run>:<script-arguments>:<file-name>:<function-name>:<function-arguments>:<debug
message>

With awk sed and grep one could easily get the specific information they are
looking for when debugging sorcery.

Any other thoughts or ideas would be great ;)


------- Additional Comments From pmahon AT sourcemage.org 2006-08-27 02:34
-------
Debugging isn't all or none. It's all, some, or none.

There is a section in libmisc which defines STD_DEBUG, although it's not used
much yet. If you just put:
$STD_DEBUG
at the top of a function it'll print the file it's in, function name, args,
line
number, and the debug message.

The problem with adding lots of debugging messages to make the debug levels
useful is that every debugging message added slows things down.

Don't forget that you are able to surpress debugging of messages from any file
by setting DEBUG_<file.>=no assuming the debug message starts with the file
it's
from.



--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



  • [SM-Sorcery-Bugs] [Bug 9514] New: Better internal debugging for sorcery, bugzilla-daemon, 08/27/2006

Archive powered by MHonArc 2.6.24.

Top of Page