https://bugs.kde.org/show_bug.cgi?id=514343
--- Comment #5 from Paul Floyd <[email protected]> --- (In reply to Philippe Waroquiers from comment #4) > Tool name and malloc replacement looks like the two most useful candidates. > Possibly there might be an interest to allow the guest to query the value of > a command line parameter > or possibly there are some tool depending things that the guest might use. > > But that is just a brainstorming discussion. If all this introduces > additional complexity, > we better focus on the two things clearly identified. Getting the tool name will be a little bit complicated. I assume that we don't want to return a pointer to host memory to the guest. That means that this will have to use an interface like GET_VBITS, taking a pointer to a client array and length and returning 0 if not running on Valgrind or the actual length (so that the client code can check that the length that they provided is large enough). -- You are receiving this mail because: You are watching all bug changes.
