* Curtis L. Olson -- Wednesday 20 March 2002 22:57: > I tried running this once myself and got lost in piles of errors > coming out of plib.
Yeah, that's the fun thing. valgrind traces =all= (de)allocations and illegal memory access through all libraries. Doing so it already detected such bugs in some very basic libs (libc, XFree, ...). Fortunately, there's a "suppression" facility, so you can exclude known and less interesting bugs. It should be possible to disable the output of any plib bugs. (Not that these weren't worth to be fixed. ;-) > I'm not sure what it is about plib that triggers > these false positives, but perhaps if you don't free memory in the > same block in which it's allocated you get a gripe? Don't know yet. > It looks interesting, especially since you don't have to recompile > your binary and every lib it links against (i.e. opengl, x11, stdc, > etc.) to make it run. Yes. There are a lot of configuration options. You can, for example, let it ask you for every bug if it should attach gdb to it right now. Lots of other stuff. And being a heavily used debugging tool in the KDE project, there is a lot of development going on. m. -- Who can afford to do professional work for nothing? What hobbyist can put three man-years into programming, finding all bugs, documenting his product, and distribute it for free? -- Bill Gates (in the mid-1970s) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
