> As far as I understand the Valgrind core, you risk introducing all > kinds of subtle issues when you try to link the Valgrind core with > libc.
Yes. Don't use libc. > In case you need a simple function from glibc, you can copy its > implementation and link it with the Valgrind core. Check first that the function does not already exist in include/pub_tool_libc*.h and coregrind/pub_core_libc*.h. > I'm afraid that > this won't work for setjmp() and longjmp() however. But did you > already have a look at the macro SCHEDSETJMP() in > coregrind/m_scheduler/scheduler.c ? Yes - just use the gcc builtins, __builtin_setmp and __builtin_lonpjmp. That works fine. J ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
