CRC mismatch (computed 19d8e52c wanted b6e98258)

[Fernando Miguel]

Binary package hint: transmission

I was running transmission-gtk from CLI and when I closed it backtraced a few errors.
I ran it with valgrind and the attached logs shows:
--24532-- Valgrind library directory: /usr/lib/valgrind
--24532-- Reading syms from /usr/bin/transmission (0x400000)
--24532-- Reading debug info from /usr/bin/transmission ..
--24532-- .. CRC mismatch (computed 19d8e52c wanted b6e98258)
--24532-- object doesn't have a symbol table
--24532-- Reading syms from /lib/ld-2.9.so (0x4000000)
--24532-- Reading debug info from /lib/ld-2.9.so ..
--24532-- .. CRC mismatch (computed 0c5a59e5 wanted 5976eeb7)
--24532-- Reading debug info from /usr/lib/debug/lib/ld-2.9.so ..
--24532-- Reading syms from /usr/lib/valgrind/amd64-linux/memcheck (0x38000000)
--24532-- object doesn't have a dynamic symbol table

$ apt-cache policy transmission-gtk
transmission-gtk:
  Installed: 1.51-0ubuntu3
  Candidate: 1.51-0ubuntu3
  Version table:
 *** 1.51-0ubuntu3 0
        500 http://darkstar.ist.utl.pt karmic/main Packages
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
Date: Sat May 16 14:54:05 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: transmission-gtk 1.51-0ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-5.6-generic
SourcePackage: transmission
Uname: Linux 2.6.30-5-generic x86_64

[Charles Kerr (charlesk)]

I've got no idea what this means. Is this a Transmission issue? an OS issue? a valgrind issue?

Also, this is in the valgrind log:

> ==25137== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 2)

Which is nice to see. :)

[Chris Coulson (chrisccoulson)]

Hey charles, I spoke to BUGabundo on IRC, and he said he saw it crash on shutdown (although the error didn't occur with this valgrind log). I'll keep this open but incomplete, just in case he can recreate the issue.

[Charles Kerr (charlesk)]

Crashing on shutdown is already ticketed upstream[1] and in Launchpad[2]. That's a long-existing issue unrelated to the CRC error... BUGabundo's shutdown problem probably ought to be addressed there rather than in this ticket.

It appears that the CRC errors have been known to show up for all stripped executables[3] and for toy "hello world" applications[4], so I'd like to see another Ubuntu user try to confirm this Ubuntu + Valgrind + Transmission CRC error before we leave this ticket open indefinitely.

[1] http://trac.transmissionbt.com/ticket/1663
[2] http://bugs.launchpad.net/bugs/319880
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425769
[4] http://ubuntuforums.org/showthread.php?t=80182

[Chris Coulson (chrisccoulson)]

charles - Yeah, we discussed it on IRC and the CRC mismatch errors seem to occur with everything (certainly, I've seen it every time I have used valgrind in the past, and i've never really considered it to be an issue).

I'll mark this as a duplicate of bug 319880 for now.

Thanks

[gcordoba (glgcg)]

Hi, I do not think it is a duplicate. I reported a bug few days ago( #419467) that shows a similar problem that appears using mpich (debuging with valgrind):

--7501-- Reading debug info from /lib/tls/i686/cmov/libc-2.9.so ..
--7501-- .. CRC mismatch (computed 7ee64c88 wanted 8d898f0d)
--7501-- object doesn't have a symbol table

 I discovered the bug when a program developed by me entered on an infinite loop. All the reports from valgrid seems to point towards the libraries libc-2.9.so and ld-2.9.so. Please, see attached file which contains the valgrind report for a simpler program that also uses mpi.