yes, valgrind was used _a_lot_ to find and fix many bugs, most of them not very serious, and just a few crushers.
however, most of the valgrind reports that we didn't get rid of seem to be rooted somewhere inside xlib ... the reports are sometimes quite bizzare. it might be that there is a real problem in xlib or that we are using xlib wrong. not many people use xlib directly these days so it is possible that it works 100% reliably only for glib, qt and motif... anyway, if you have expertize to research those valgrind reports, by all means please do! bye andraz On Thu, 2006-08-17 at 13:49 -0600, m h wrote: > I started messing around with valgrind last night. (It actually makes > cinelerra more stable, though unbearably slow). > > One of my crashes (putting more than one concert hall effects on the > audio) crashes cinelerra, but not while running under valgrind. When > I get some time, I'll post the results, I need some help to debug > this. > > Also, there appear to be lots of leaks that valgrind is reporting > (this is gentoo cinelerra cvs 2.0). Has anyone made any attempt to > deal with valgrind? > > I figure if I'm going to be doing klocwork, coverity stuff, valgrind > is up that alley too. > > I guess I need to learn about pthreads and refresh on my c++. > > -matt > > _______________________________________________ > Cinelerra mailing list > [email protected] > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
