|
From: Julian S. <js...@ac...> - 2010-02-15 09:18:24
|
On Monday 15 February 2010, Tom Hughes wrote: > On 15/02/10 08:23, stecca michele wrote: > > Hi all... > > The problem is not related to the CRC error but to JAVA 1.6. > > I successfully used Valgrind with a C program and with a JAVA 1.5 too. > > The problem is related to JAVA 1.6. I tried to run it with the > > --tool=cachegrind and --trace-children=yes options enabled but I get the > > following error: > > The error just means that your debug packages are out of date and don't > match your main packages. It won't actually stop anything working but it > may mean that the backtraces reported for errors are not accurate. I think there's more to it than that though. I see this a lot on Ubuntu, eg: --4274-- Reading debug info from /lib/libc-2.10.1.so .. --4274-- .. CRC mismatch (computed e2035481 wanted a2d8b96b) --4274-- Reading debug info from /usr/lib/debug/lib/libc-2.10.1.so .. So first it tries to read the debug info from the main .so, complains about a CRC mismatch, and then reads from the debug .so, and what it gets from that seems to me to be fine. So I'm not sure what's going on there. This happens even with clean installs of Ubuntu so I would have thought it unlikely to really be a mismatch. J |