|
From: Patrick O. <pat...@in...> - 2006-07-07 12:10:54
|
On Fri, 2006-07-07 at 10:41 +0000, Oleksandr K. wrote: > Julian Seward <jseward <at> acm.org> writes: > > As a result of recent memcheck hackery in the 3.0 line, I broke > > support for the VALGRIND_SET_VBITS and VALGRIND_GET_VBITS > > client requests. I haven't fixed them; instead I am hoping to > > get rid of them altogether. They were introduced as an experimental > > hack, and as far as I know nobody ever used them. > > > > So my question is: does anybody use these? > > > > If you haven't a clue what this is about, it's a pretty safe bet > > you don't use them. > > > > Hi, > > I do need the GET/SET VBITS requests! They are supported again since at least 3.2.0. Just beware that the client request mechanism has changed and therefore you have to use the header files from that valgrind version to use the new requests. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. |