Simon Barner <[EMAIL PROTECTED]> wrote:
> I finally fixed the valgrind build with gcc 4.2. Could you
> please verify that
>
>a) the port also build on 7-current,
>b) that there are no regressions (I did a quick test on 6.2,
> and it seems to work).
I didn't notice any regressions o
Teufel wrote:
> Hi,
>
> tried both patches on today's 7-CURRENT. Both compile, but using
> valgrind ends in a crash with unhandled syscalls.
Ok, thanks for the report.
> >http://home.leo.org/~barner/freebsd/valgrind-snapshot.patch
> >http://home.leo.org/~barner/freebsd/valgrind.patch
I've upda
On Tuesday 10 July 2007, Simon Barner wrote:
> > Thank you, would it build in AMD64?
>
> I'm afraid, the port is i386 only. There were rumors that Peter Wemm
> is working on port of valgrind 3.x, but I am not sure of the status
> of this effort (which certainly involves a lot of work).
FWIW, valgr
> Thank you, would it build in AMD64?
I'm afraid, the port is i386 only. There were rumors that Peter Wemm is
working on port of valgrind 3.x, but I am not sure of the status of
this effort (which certainly involves a lot of work).
--
Best regards / Viele Grüße, [EMAI
On 7/10/07, Simon Barner <[EMAIL PROTECTED]> wrote:
Hello,
I finally fixed the valgrind build with gcc 4.2. Could you
please verify that
a) the port also build on 7-current,
b) that there are no regressions (I did a quick test on 6.2,
and it seems to work).
http://home.leo.org/~bar
Hello,
I finally fixed the valgrind build with gcc 4.2. Could you
please verify that
a) the port also build on 7-current,
b) that there are no regressions (I did a quick test on 6.2,
and it seems to work).
http://home.leo.org/~barner/freebsd/valgrind-snapshot.patch
http://home.leo.or
