Ok, there has been a lot of confusion about debug flags and trace
flags. I changed the way the flags stuff worked from a compile
perspective which required me to make changes throughout the tree, so
I took the opportunity to rename the trace flags to debug flags. The
idea behind the change was
So, I think part of the confusion is that there are two names now,
debug flags and trace flags, but they're different views of the same
mechanism (yes? no?) It seems like the --trace* options are like the
--debug* options, except their intended use is a subset of --debug*,
specifically
On my phone, so I'll be brief, but just fixing the scons to be consistent
sounds good to me.
On Jun 1, 2011 6:55 PM, Gabriel Michael Black gbl...@eecs.umich.edu
wrote:
So, I think part of the confusion is that there are two names now,
debug flags and trace flags, but they're different views of
OK, now that I'm at a keyboard: if we change the scons thing from
TraceFlag() to DebugFlag(), then there's one set of flags with one set
of names, it's all debug flags. Some (currently most) of them are
only used to control DPRINTFs, but they could be used for other
things, and the same flag
I'll post a diff to fix the SCons stuff very soon. Just compiling
stuff to make sure it works.
The biggest problem with two namespaces is that it's a lot of code to
manage to support both of them. The debug flags stuff is all over the
place: scons to generate the flags files, command line
