On Feb 13, 2008 7:31 PM, Philippe Waroquiers <[EMAIL PROTECTED]> wrote: > Currently, I am working on doing this because it is fun. > I understood from the doc that it is not ok to call libc or any system call > directly in valgrind core, because this > causes various subtile problems. > > Are these problems reasonable enough that a "quick and dirty" prototype > could use libc ? > (so, typically; directly call strlen or directly call a "read" or "write" > system call)
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. In case you need a simple function from glibc, you can copy its implementation and link it with the Valgrind core. 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 ? Bart. ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
