ports/86007: devel/valgrind won't work on 6.x but does on 5.x
Ulrich Spoerlein
q at galgenberg.net
Mon Sep 12 08:20:14 UTC 2005
>Number: 86007
>Category: ports
>Synopsis: devel/valgrind won't work on 6.x but does on 5.x
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Sep 12 08:20:12 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Ulrich Spoerlein
>Release: FreeBSD 6.0-BETA2 i386
>Organization:
>Environment:
>Description:
Synopsis says it all. Something changed in 6.x which makes valgrind fail,
which is rather sad, since it is such a cool tool.
>How-To-Repeat:
Just install devel/valgrind and run something like ls(1)
% valgrind ls
==1629== Memcheck, a memory error detector for x86-linux.
==1629== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==1629== Using valgrind-2.1.0, a program supervision framework for x86-linux.
==1629== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==1629== Estimated CPU clock rate is 601 MHz
==1629== For more details, rerun with: -v
==1629==
valgrind: the `impossible' happened:
Unhandled sysarch call
Basic block ctr is approximately 0
==1629== at 0xB802BE91: (within /usr/local/lib/valgrind/stage2)
==1629== by 0xB802BE90: (within /usr/local/lib/valgrind/stage2)
==1629== by 0xB802BEA8: vgPlain_core_panic (in /usr/local/lib/valgrind/stage2)
==1629== by 0xB80341A1: (within /usr/local/lib/valgrind/stage2)
sched status:
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==1629== at 0x3C00FD3F: (within /libexec/ld-elf.so.1)
==1629== by 0x3C0048F9: allocate_initial_tls (in /libexec/ld-elf.so.1)
==1629== by 0x3C007165: _rtld (in /libexec/ld-elf.so.1)
==1629== by 0x3C0043CD: (within /libexec/ld-elf.so.1)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list