Hi!
On Jul 11, 2008, at 4:40 PM, MARK CALLAGHAN wrote:
exit message. But if you remove the DBUG_PRINT uses, then you lose a
bit of knowledge.
assert() have been kept.
If we had a really good method for doing this that did not involve the
current issues with libdbug, Jay has all of the DBUG done in one tree.
We could do a single reverse patch that stripped out all enter and exit.
I agree with most, we should start at ground zero for the most part.
The current system was buying us more headaches then good will. The
optimizer guys had already forked their one DBUG code into the server,
so the system was more then a little messy.
Cheers,
-Brian
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]
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
