Hi, Michael Abshoff, > I applied your patch against a vanilla 3.3.0 and with both gcc 4.2 and a > recent gcc 4.3 snapshot I get the following compilation failure on Linux > x86-64 (Centos 5)
> m_syswrap/syswrap-linux.c: In function ‘vgModuleLocal_do_fork_clone’: > m_syswrap/syswrap-linux.c:338: error: ‘VexGuestArchState’ has no member > named ‘guest_EAX’ So far, compiling has used gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-27) on i686 only. I will try the gcc on Fedora 8, and work towards separating platform-dependent code better. In the meantime, please use i686 only. [Perhaps -m32 will work on x86_64 ?] >>Motivated in part by the difficulty of tracking down the causes of >>"Conditional jump or move depends on uninitialised data", the patches >>include a new *optional* mode for memcheck: --complain-asap=yes. > This is a very, very cool feature. Any way you can split that patch out > from the patchset? Yes, producing a separate patch for this feature is on the list of tasks to do. In the meantime, nearly all of this feature is in just one file memcheck/mc_main.c. Perhaps if you apply the patch for just that one file, and make minimal adjustments as needed, then you may be able to use the feature separately. -- John Reiser, [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
