Re: [Valgrind-developers] Unsupported clone() flags: 0x800111

Hello Konstantin, >>My patches for valgrind to support UserModeLinux implemented >>a CLONE_CHILD_LETGO flag meaning, "do not virtualize the child; >>let it run natively free." This happened to be a good idea for UML. > May I ask you to send me this patch? > If I understood you correctly, I need

[Valgrind-developers] 2008-02-07 03:15:02 GMT nightly build (alvis, i686, Red Hat 7.3)

Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-02-07 03:15:02 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2008-02-07 03:20:11 GMT nightly build (aston, x86_64, Fedora Core 5)

Nightly build on aston ( x86_64, Fedora Core 5 ) started at 2008-02-07 03:20:11 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

[Valgrind-developers] 2008-02-07 03:25:16 GMT nightly build (trojan, x86_64, Fedora Core 6)

Nightly build on trojan ( x86_64, Fedora Core 6 ) started at 2008-02-07 03:25:16 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

[Valgrind-developers] 2008-02-07 03:05:04 GMT nightly build (lloyd, x86_64, Fedora 7)

Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-02-07 03:05:04 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ...

[Valgrind-developers] 2008-02-07 03:10:06 GMT nightly build (dellow, x86_64, Fedora 8)

Nightly build on dellow ( x86_64, Fedora 8 ) started at 2008-02-07 03:10:06 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2008-02-07 03:00:03 GMT nightly build (gill, x86_64, Fedora Core 2)

Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-02-07 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

Re: [Valgrind-developers] Unsupported clone() flags: 0x800111

John, > My patches for valgrind to support UserModeLinux implemented > a CLONE_CHILD_LETGO flag meaning, "do not virtualize the child; > let it run natively free." This happened to be a good idea for UML. May I ask you to send me this patch? If I understood you correctly, I need something simila

Re: [Valgrind-developers] Experimental Valgrind coverage tool

On Wednesday 06 February 2008, Nicholas Nethercote wrote: > On Tue, 5 Feb 2008, Josef Weidendorfer wrote: > > > How similar is the format for VCov to cachegrind's? I suppose this > > only needs a further "event" for a source line: whether there is debug info > > or not. > > It's simpler than Cach

[Valgrind-developers] vex: r1808 - in trunk: priv/guest-amd64 priv/host-amd64 priv/host-generic priv/ir pub

Author: sewardj Date: 2008-02-06 11:42:45 + (Wed, 06 Feb 2008) New Revision: 1808 Log: Add SSSE3 support. Currently only for 64-bit. TODO: * Check through IR generation * For 128-bit variants accessing memory, generate an exception if effective address is not 128-bit aligned * Change CPUI

Re: [Valgrind-developers] [Valgrind-users] memcheck tool related query for multithreadedapplication

On Feb 6, 2008 1:59 AM, richa <[EMAIL PROTECTED]> wrote: > a) I have checked again, am compiling the entire source code with "-g" > option. So I think the debug info will not be any problem. Time to show us your code. If you can't show the real app, show a toy app that has the same problem. In t