[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#425769: marked as done (libc6-i686: valgrind detects CRC error in package)

Your message dated Tue, 25 Apr 2023 21:21:33 +0200
with message-id <ZEgoPc03zwWwJ/F3@aurel32.net>
and subject line Re: Bug#425769: libc6-i686: valgrind detects CRC error in package
has caused the Debian Bug report #425769,
regarding libc6-i686: valgrind detects CRC error in package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
425769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425769
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-i686
Version: 2.3.6.ds1-13
Severity: normal


When running a program under the valgrind memory-allocation debugger,
I got the following error messages:

--3777-- Reading syms from /lib/tls/i686/cmov/libm-2.3.6.so (0x4028000)
--3777-- Reading debug info from /lib/tls/i686/cmov/libm-2.3.6.so...
--3777-- ... CRC mismatch (computed 70BA299D wanted 3AF3BB73)
--3777--    object doesn't have a symbol table
--3777-- Reading syms from /lib/tls/i686/cmov/libc-2.3.6.so (0x404E000)
--3777-- Reading debug info from /lib/tls/i686/cmov/libc-2.3.6.so...
--3777-- ... CRC mismatch (computed 997A732C wanted BFAEF692)
--3777--    object doesn't have a symbol table

These symbol-table files belong to libc6-i686, so I assume that's where
the problem is.  Another possibility might be that valgrind is expecting
the symbol tables from the regular (un-optimized for i686) libraries.

I re-installed the libc6-i686 package and got the same messages, so I
don't think this is a file-corruption issue.

		-- A.T.Young   (aty@mintaka.sdsu.edu)


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages libc6-i686 depends on:
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries

libc6-i686 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.24-15

On 2007-05-23 13:42, Andrew T. Young wrote:
> Package: libc6-i686
> Version: 2.3.6.ds1-13
> Severity: normal
> 
> 
> When running a program under the valgrind memory-allocation debugger,
> I got the following error messages:
> 
> --3777-- Reading syms from /lib/tls/i686/cmov/libm-2.3.6.so (0x4028000)
> --3777-- Reading debug info from /lib/tls/i686/cmov/libm-2.3.6.so...
> --3777-- ... CRC mismatch (computed 70BA299D wanted 3AF3BB73)
> --3777--    object doesn't have a symbol table
> --3777-- Reading syms from /lib/tls/i686/cmov/libc-2.3.6.so (0x404E000)
> --3777-- Reading debug info from /lib/tls/i686/cmov/libc-2.3.6.so...
> --3777-- ... CRC mismatch (computed 997A732C wanted BFAEF692)
> --3777--    object doesn't have a symbol table
> 
> These symbol-table files belong to libc6-i686, so I assume that's where
> the problem is.  Another possibility might be that valgrind is expecting
> the symbol tables from the regular (un-optimized for i686) libraries.
> 
> I re-installed the libc6-i686 package and got the same messages, so I
> don't think this is a file-corruption issue.

The libc6-i686 package has been removed in glibc 2.24-15. Closing the
bug accordingly.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

--- End Message ---
Reply to: