Are you removing all of the DBUG macros now or converting them? DBUG_ENTER should be cheap to bring back and even cheaper to convert now. DBUG_EXIT should not exist. Use a C++ with a class for which the constructor prints the enter message and the destructor prints the exit message. But if you remove the DBUG_PRINT uses, then you lose a bit of knowledge.
On Fri, Jul 11, 2008 at 1:20 PM, Brian Aker <[EMAIL PROTECTED]> wrote: > Hi! > > I would like to see us find someone who has a good library which has thread > support which does not require us to dink up the pthread library in order > for us to use it. Preferably something we can get a distribution to pick up > for packaging. > > Cheers, > -Brian > > On Jul 11, 2008, at 1:02 PM, MARK CALLAGHAN wrote: > >> I will be happy with any tracing capability. One of the early messages >> mentioned using a debugger in place of tracing, and that would be >> awful for diagnosing behavior. > > -- > _______________________________________________________ > Brian "Krow" Aker, brian at tangent.org > Seattle, Washington > http://krow.net/ <-- Me > http://tangent.org/ <-- Software > _______________________________________________________ > You can't grep a dead tree. > > > > -- Mark Callaghan [EMAIL PROTECTED] _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
