Kailash Sethuraman
2005-11-24 12:49:11 UTC
Hi guys,
I think its fair to say that after some period of no work at all, we
are atleast doing something these days. I merged in syswrap-generic.c
, however it would be good if one of you could take a look at our
syswrap-generic vs the one in valgrind's trunk to ensure that I have
not broken anything, in terms of our own netbsd specificness as well
as possibly missed merges.
It is not in a state where it compiles yet. I suspect other files will
need to be merged as well.
Peter do you have any idea on what these might be? Perhaps a list of
files that need to be merged?
Then we can get on it, get valgrind compiling. I think this merge will
provide us with nullgrind, so we dont have to deal with memcheck
injecting heavy instrumentation code. We can deal with a program
simply running under valgrind first.
We should do more regular/quick merges, now that we have discovered
how easy it is with edfiff.
What do you guys think?
Regards,
Kailash
I think its fair to say that after some period of no work at all, we
are atleast doing something these days. I merged in syswrap-generic.c
, however it would be good if one of you could take a look at our
syswrap-generic vs the one in valgrind's trunk to ensure that I have
not broken anything, in terms of our own netbsd specificness as well
as possibly missed merges.
It is not in a state where it compiles yet. I suspect other files will
need to be merged as well.
Peter do you have any idea on what these might be? Perhaps a list of
files that need to be merged?
Then we can get on it, get valgrind compiling. I think this merge will
provide us with nullgrind, so we dont have to deal with memcheck
injecting heavy instrumentation code. We can deal with a program
simply running under valgrind first.
We should do more regular/quick merges, now that we have discovered
how easy it is with edfiff.
What do you guys think?
Regards,
Kailash