|
From: Neeraj K. <kum...@gm...> - 2006-04-12 22:41:20
|
Hi,
I wanted to use helgrind for the project which I am doing but it is giving
me the following message.
--------------------
Helgrind is currently not working, because:
(a) it is not yet ready to handle the Vex IR and the use with 64-bit
platforms introduced in Valgrind 3.0.0
(b) we need to get thread operation tracking working again after
the changes added in Valgrind 2.4.0
Sorry for the inconvenience. Let us know if this is a problem for you.
--------------------
The machine I'm using is
$: uname -a
Linux pearl 2.4.21-37.ELsmp #1 SMP Wed Sep 7 13:28:55 EDT 2005 i686 i686
i386 GNU/Linux
Its a 32 bit machine and the valgrind version is valgrind-3.1.1. So what
does the error message means. Won't I be able to use helgrind on this
machine.
Please note that I have been using memcheck, massif etc. nicely. Please let
me know what I need to do to get helgrind working.
Any quick help will be of great value to me.
Thanks, in advance,
Kumar Neeraj
|
|
From: Nicholas N. <nj...@cs...> - 2006-04-12 22:54:16
|
On Wed, 12 Apr 2006, Neeraj Kumar wrote: > I wanted to use helgrind for the project which I am doing but it is giving > me the following message. > -------------------- > Helgrind is currently not working, because: > (a) it is not yet ready to handle the Vex IR and the use with 64-bit > platforms introduced in Valgrind 3.0.0 > (b) we need to get thread operation tracking working again after > the changes added in Valgrind 2.4.0 > > Sorry for the inconvenience. Let us know if this is a problem for you. > -------------------- Helgrind has been broken since Valgrind 2.2.0. If you want to use it, you'll have to use 2.2.0. Work is underway to unbreak Helgrind, but it's a slow process. Nick |
|
From: Dennis L. <pla...@in...> - 2006-04-18 23:39:56
|
Am Donnerstag, den 13.04.2006, 08:54 +1000 schrieb Nicholas Nethercote: > Helgrind has been broken since Valgrind 2.2.0. If you want to use it, > you'll have to use 2.2.0. Work is underway to unbreak Helgrind, but it's a > slow process. What takes so long, and how can we speed it up? I read some promise in the svn files to have valgrind in 3.2, but then it was cancelled, despite the function redirection working now, which was said to be the reason that helgrind does not work anymore. If its not working properly, but could be of preliminary use, maybe you can document somewhere how to enable it? Or give an estimate how long it will take, what needs to be done, and most important, whats the easiest way for the community to be of help (beside presenting a patch that makes it work again) greets Dennis |
|
From: Jim C. <jim...@gm...> - 2006-04-19 03:53:57
|
Dennis Lubert wrote: > Am Donnerstag, den 13.04.2006, 08:54 +1000 schrieb Nicholas Nethercote: > > >> Helgrind has been broken since Valgrind 2.2.0. If you want to use it, >> you'll have to use 2.2.0. Work is underway to unbreak Helgrind, but it's a >> slow process. >> > > What takes so long, and how can we speed it up? I read some promise in > the svn files to have valgrind in 3.2, but then it was cancelled, > despite the function redirection working now, which was said to be the > reason that helgrind does not work anymore. If its not working properly, > but could be of preliminary use, maybe you can document somewhere how to > enable it? Or give an estimate how long it will take, what needs to be > done, and most important, whats the easiest way for the community to be > of help (beside presenting a patch that makes it work again) > > greets > > Dennis > > 2 possibilities occur to me: Pay Julian or Nick enough that he can shelve his current paying work (if thats even possible for them). This might not be an option, given your uni email addy. Submit a Summer-of-Code proposal to Google, or solicit some exceptional university student to do so. Julian will undoubtedly have the most informed view on what the scope of this might be. |