Re: Valgrind GCC 4.2 patches

Hi,

tried both patches on today's 7-CURRENT. Both compile, but using 
valgrind ends in a crash with unhandled syscalls.
I think there is a bit more left to fix. But I still hope to see soon a 
working valgrind on 7-CURRENT.

Greetings,

Stephan

a simple valgrind /bin/ls puts out:

==66330== Memcheck, a memory error detector for x86-linux.
==66330== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==66330== Using valgrind-2.1.0, a program supervision framework for 
x86-linux.
==66330== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==66330== Estimated CPU clock rate is 2440 MHz
==66330== For more details, rerun with: -v
==66330==
--66330-- WARNING: unhandled syscall: 477
--66330-- Do not panic.  You may be able to fix this easily.
--66330-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
==66330== Warning: client syscall munmap tried to modify addresses 
0xFFFFFFDA-0xE2
--66330-- WARNING: unhandled syscall: 477
--66330-- Do not panic.  You may be able to fix this easily.
--66330-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
==66330== Invalid write of size 4
==66330==    at 0x3C007B93: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C0179B5: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C007D9C: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C005F7B: (within /libexec/ld-elf.so.1)
==66330==  Address 0xFFFFFFFC is not stack'd, malloc'd or free'd
==66330==
==66330== Process terminating with default action of signal 10 (SIGBUS): 
dumping core
==66330==    at 0x3C007B93: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C0179B5: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C007D9C: (within /libexec/ld-elf.so.1)
==66330==    by 0x3C005F7B: (within /libexec/ld-elf.so.1)
==66330== Core dumping not implemented. Please re-run valgrind after 
fixing the crash.
==66330==
==66330== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
==66330== malloc/free: in use at exit: 0 bytes in 0 blocks.
==66330== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==66330== For a detailed leak analysis,  rerun with: --leak-check=yes
==66330== For counts of detected errors, rerun with: -v

Simon Barner wrote:
> Hello,
>
> I finally fixed the valgrind build with gcc 4.2. Could you
> please verify that
>
> http://home.leo.org/~barner/freebsd/valgrind-snapshot.patch
> http://home.leo.org/~barner/freebsd/valgrind.patch
>
> Thanks for you feedback,
>  Simon
>
> (f'up2 freebsd-ports )
>