|
From: Oliver S. <ol...@f-...> - 2010-07-27 14:34:16
Attachments:
signature.asc
|
Hi, I noticed that Ubuntu 10.04 now contains a Valgrind version dubbed Valgrind-3.6.0.SVN-Debian and that when I run my code under it, I get: "Valgrind: fatal error - cannot continue: use of the deprecated client requests VG_USERREQ__PRINTF or VG_USERREQ__PRINTF_BACKTRACE on a platform where they cannot be supported. Please use the equivalent _VALIST_BY_REF versions instead. This is a binary-incompatible change in Valgrind's client request mechanism. It is unfortunate, but difficult to avoid. End-users are expected to almost never see this message. The only case in which you might see this message is if your code uses the macros VALGRIND_PRINTF or VALGRIND_PRINTF_BACKTRACE. If so, you will need to recompile such code, using the header files from this version of Valgrind, and not any previous version." 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. Thanks, // Oliver |
|
From: Julian S. <js...@ac...> - 2010-07-27 15:02:08
|
> 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 |
|
From: Oliver S. <ol...@f-...> - 2010-07-27 17:49:05
Attachments:
signature.asc
|
On 2010-07-27 15:04, Julian Seward wrote: > 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. Thanks for the clarification, Julian. In this case I'll return to 3.5.0 on that machine by trying to build it ... if that works. Heard that there were issues building it on Ubuntu 10.04 (probably due to this change in GCC) which probably prompted them to use the newer SVN code in the first place. Thanks, // Oliver |