Hello
I am working on a patch that increases the verbosity of the
modules/debugger module . What I am doing is very simple, but in my
opinion effective :
I am also printing the action being run, not just the type(in the new
descr field)
Feb 9 16:46:03 marius ../../ser[32588]: ERROR: *** cfgtrace:
c=[../unit/30.cfg] l=26 a=17 descr=if (type<22>) {} else {};
Feb 9 16:46:03 marius ../../ser[32588]: ERROR: *** cfgtrace:
c=[../unit/30.cfg] l=30 a=17 descr=if (type<22>) {} else {};
Feb 9 16:46:03 marius ../../ser[32588]: ERROR: *** cfgtrace:
c=[../unit/30.cfg] l=26 a=28 descr=
external_module_call(f_ptr<0xb7d4dbf8>, 5, type<10>);
First off all the trace is not very informative because I don't have
that of a good example but you get the point.
I know it would be easy to read the cfg and get the line number, but
what if you have multiple commands per line. And printing the action
type for me is not really usefull (need to get back to header to check
the action type).
What do you think, it will be usefull as such? The patch(still some
lines to go) if fairly big but fullproof (the print_action()
print_expression() in route_struct.c will output data in a static buffer
instead of calling DBG()).
Cheers
Marius