> Nothing unusual about getting the message, as the headers contained in > our VCS are from 3.5.0. However, what I was wondering now is whether it > is possible to update the headers in our VCS and whether it is going to > work on older Valgrind versions. Basically all other Valgrind > installations we have are still at the 3.5.0 release version.
Unfortunately, no. (sigh.) - headers 3.5.0 and use client requests VG_USERREQ__PRINTF / VG_USERREQ__PRINTF_BACKTRACE, which 3.6.0-SVN refuses to handle. Basically, at some point (gcc-4.4/4.5 ?) the defintion of va_list changed so that the 3.5.0 scheme simply didn't work any more -- it didn't even compile. - headers 3.6.0.SVN use client requests VG_USERREQ__PRINTF_VALIST_BY_REF / VG_USERREQ__PRINTF_BACKTRACE_VALIST_BY_REF which 3.5.0 has never heard of, and so doesn't handle. J ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
