skaller wrote: > > 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.
Really? I haven't used valgrind with a higher-level language such as ocaml, but since valgrind operates on x86 (and powerpc) object code, then I can't think of any reason why it wouldn't work just as well with ocaml. The only thing that would be different is that the debugging symbols that get printed out might not be as meaningful. So, yes, I guess that would make it less useful. It would still tell you about a bug, but if ocaml (et al.) don't produce the kind of debugging symbols that valgrind is used to then the report that the human sees might be the same as if the program had been compiled without debug info. See also: oprofile, the slickest performance profiler around, which likewise operates at the machine language level. Regards, Zooko ------------------------------------------------------------------------- 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
