|
From: Nicholas N. <nj...@cs...> - 2005-07-19 01:18:05
|
On Sat, 9 Jul 2005, Kailash Sethuraman wrote: > I am working on porting valgrind to netbsd/i386. I actually started > working with the FreeBSD port of Valgrind 2.x, I have done a bit of > work on it already and I am currently struggling with the OS specifics > in coregrind/vg_scheduler.c > > However, I am convinced that I should concentrate on porting the 3.x > line. As I currently do not have a linux box at hand ( I am working on > that) to test the valgrind's development line I have a few doubts. > > I intend to grab a snapshot of valgrind 3.x and work on it, and sync > semi-regularly with the svn repo. Is the current 3.x line for > linux/i386 in a good enough state to use as a template for the OS > port? Yes. Working from the 3.x repository is the right thing to do. Syncing semi-regularly is also a good idea. > Is there anything I should definitely know thats not in the > documentation before going off on porting it? The internal workings of > valgrind are still hazy to me. Working from the FreeBSD port is a good idea, even though Valgrind's internals have changed a lot since 2.x. Porting Valgrind to a new OS is not for the faint-hearted, although it has been done successfully by others :) Good luck! N |