I cleaned up the freebsd diffs, added some magic from this thread, and
filed a debbug about it (702729). I'm not 100% confident it won't cause
some debian/linux regression or that it's complete, but it's a step in
the right direction, particularly as it builds off of the version of
valgrind presen
It looks like freebsd9 ports has "valgrind-snapshot" which is based off of
valgrind 3.8.0:
http://cdn.bitbucket.org/stass/valgrind-freebsd/downloads/valgrind-freebsd-3.8.0.tar.bz2
There are a lot more changes than I would expect between this and the
upstream 3.8.0 tarball:
valgrind-3.8.0/FAQ.txt
On Thu, Mar 07, 2013 at 09:00:42PM +0100, Carlos Alberto Lopez Perez wrote:
> I'm not sure if this means that we can finally have valgrind packaged
> for Debian/kFreeBSD.
>
>
> The diffstat between "official" valgrind and this freebsd port is pretty
> big.
Is there any chance that the author(s)
On 07/03/13 19:51, Jeff Epler wrote:
> On Thu, Mar 07, 2013 at 05:49:55PM +0100, Petr Salinger wrote:
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
>>>
>>> Aha. eglibc is testing that the syscall s
On Thu, Mar 07, 2013 at 05:49:55PM +0100, Petr Salinger wrote:
> >>Valgrind does appear to be aware of sysarch, implementing
> >>sysarch(AMD64_SET_FSBASE) in
> >>coregrind/m_syswrap/syswrap-amd64-freebsd.c.
> >
> >Aha. eglibc is testing that the syscall succeeds, which is indicated by
> >setting R
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Aha. eglibc is testing that the syscall succeeds, which is indicated by
setting RAX to 0.
The standard kernel in a success case sets RAX to zero
and clears carry
On Thu, Mar 07, 2013 at 09:40:38AM -0600, Jeff Epler wrote:
> Valgrind does appear to be aware of sysarch, implementing
> sysarch(AMD64_SET_FSBASE) in
> coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Aha. eglibc is testing that the syscall succeeds, which is indicated by
setting RAX to 0.
Valgrind does appear to be aware of sysarch, implementing
sysarch(AMD64_SET_FSBASE) in
coregrind/m_syswrap/syswrap-amd64-freebsd.c.
Jeff
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://
The error message does not come from valgrind, but from the libc.
I fixed the paths and rebuilt it with --disable-tls
Unfortunately nothing changed: the same error
I tried it also with --enable-tls (just in case) and also same error :(
May be valgrind should know about sysarch syscall.
It is
On 05/03/13 20:40, Petr Salinger wrote:
>> The error message does not come from valgrind, but from the libc.
>>
>> According to [0], FreeBSD fully supports TLS only on i386 and ia64
>> which kinda
>> explains why your amd64 build does not run (that page looks old
>> though). Try
>> disabling TLS ex
The error message does not come from valgrind, but from the libc.
According to [0], FreeBSD fully supports TLS only on i386 and ia64 which kinda
explains why your amd64 build does not run (that page looks old though). Try
disabling TLS explicitly on the valgrind build by passing --disable-tls to
On Tue, Mar 05, 2013 at 06:36:26PM +0100, Carlos Alberto Lopez Perez wrote:
> Hi!
>
> From some time ago there is available a port of Valgrind to FreeBSD [1]
>
> I tried to compile it on Debian/kFreeBSD, and after some patching
> I was able to compile it on kfreebsd-amd64 sid (didn't tested i386)
Hi!
From some time ago there is available a port of Valgrind to FreeBSD [1]
I tried to compile it on Debian/kFreeBSD, and after some patching
I was able to compile it on kfreebsd-amd64 sid (didn't tested i386).
Here are some quick instructions to replicate what I did
(valgrind_kfreebsd.patch is
13 matches
Mail list logo
