On Fri, 2007-05-25 at 10:48 -0600, [EMAIL PROTECTED] wrote: > John Skaller wrote:
> > I've spent around 2 days trying to figure out what's going > > on and can't. [btw: i finally did figure it out] > Valgrind is an excellent tool which often tells you exactly what the bug is, > and almost never wastes your time with false alarms. It's way better than > older memory-bug-finding tools that you may have used, like Purify. Give > Valgrind a try. > Regards, > > Zooko > P.S. This advertisement brought to you by People For The Advancement of the > Use of Valgrind. I have no financial interest in Valgrind -- I'm just a happy > user. Hehe .. I've used Valgrind once or twice. However normally I do not use debugging tools of any kind at all, I just use embedded print statements, code study, and peer review. This is mainly because I don't normally write code in C, unless I really have to, and Valgrind, gdb, etc, are fairly useless with code generated by higher level tools like Ocaml. Of course Ocaml has its own debugger.. but i don't use that either. I prefer universal, platform independent techniques that don't rely on messing about with debugging tools. Which is all a way of saying I'm lazy .. :) -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
