[Ns-bugs] [Bug 164] Config calls which take a string can fail silently
bugzilla-daemon at nsnam-www.ece.gatech.edu
Wed Apr 9 13:45:09 PDT 2008
------- Comment #1 from mathieu.lacage at sophia.inria.fr 2008-04-09 16:45 -------
(In reply to comment #0)
> At the least, they need to output a warning message that says something like
> "Config couldn't match the string XXX to an (attribute|trace source)". These
> kind of output messages are enabled only if logging is enabled; it'd be nice to
> have the messages that indicate a failure to be output unconditionally.
The whole system works under the assumption that matching failures are not
errors: it is impossible to tell the difference between a match failure due to
a user typo or misunderstanding and a match failure due to the fact that the
user requested a different trace source than the one present in a specific
So, the bottomline is that yes, the current system makes it hard to debug match
failures but there is no simple solution to that problem which does not suck.
What is needed is something which returns a user-understandable report about
what matched, what did not match and why and the debugging output is none of
that. The hardest part here is first defining precisely the output you want to
get. Implementing the error report generation is not especially hard once we
have defined that.
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Ns-bugs