|
From: Philippe W. <phi...@sk...> - 2011-12-08 21:01:05
|
> I'm working on a memory trace visualization tool, currently based on > either Lackey or a simple modification of it that writes binary data > rather than ascii. I'm wondering what would be the fastest and best > supported way to export large volumes of online data from a valgrind > tool to another process. My tests seem to show that shared memory is > the best route, but due to the limited system library support in > valgrind I was unable to port this interface into a tool. Any ideas? There is support for shared memory in Valgrind : shared memory is used between the embedded Valgrind 3.7.0 gdbserver and the vgdb relay application (vgdb relays data between gdb and Valgrind gdbserver). See e.g. file coregrind/m_gdbserver/remote-utils.c usage of VG_(am_shared_mmap_file_float_valgrind). See pub_core_aspacemgr.h and pub_tool_aspacemgr.h for the available shared memory related functionalities. Philippe |