|
From: Raphael Z. <zu...@iz...> - 2005-07-20 15:08:50
|
hi! I googled around, but couldn't find any related posts... Has someone ever though about a windows port of valgrind? I don't say that I would start doing it, but I'm at least interested in doing such a project together with my colleague... Imagine we would now start studying the valgrind source, is there a chance to port valgrind to windows at all? what are the problems? It would help, if you could list all problematic things that you can imagine of. Or the other question: Is anyone already porting it to windows and could need some help? If yes, what kind of help (no, we don't like to document things ;-)) thanks, Raphael |
|
From: Nicholas N. <nj...@cs...> - 2005-07-20 15:15:39
|
On Wed, 20 Jul 2005, Raphael Zulliger wrote: > Has someone ever though about a windows port of valgrind? I don't say that I > would start doing it, but I'm at least interested in doing such a project > together with my colleague... > Imagine we would now start studying the valgrind source, is there a chance to > port valgrind to windows at all? what are the problems? It would help, if you > could list all problematic things that you can imagine of. > > Or the other question: Is anyone already porting it to windows and could need > some help? If yes, what kind of help (no, we don't like to document things > ;-)) Someone named KJK::Hyperion discussed this in some depth on the valgrind-developers list in late February/early March last year in a thread called "Developing Valgrind for Windows". The short answer is: it would be *very* difficult, as Valgrind has many UNIX assumptions. To make it work at all, I believe large parts of Valgrind would have to be rewritten, enough to almost warrant a separate project. N |
Quoting Raphael Zulliger <zu...@iz...>: > hi! > > I googled around, but couldn't find any related posts... > > Has someone ever though about a windows port of valgrind? I don't say > that I would start doing it, but I'm at least interested in doing such a > project together with my colleague... > Imagine we would now start studying the valgrind source, is there a > chance to port valgrind to windows at all? what are the problems? It > would help, if you could list all problematic things that you can > imagine of. Mojo and DynamoRIO are two tools that works in windows, but neither of them are open-source. You may want to have a look at their work to have an idea of the problems. Mojo: http://www.cs.washington.edu/homes/lerns/mojo.pdf DynamoRIO: http://www.cag.lcs.mit.edu/dynamorio/ > > Or the other question: Is anyone already porting it to windows and could > need some help? If yes, what kind of help (no, we don't like to document > things ;-)) > > thanks, Raphael > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |