|
From: Yossi K. <yos...@gm...> - 2008-01-07 16:50:02
|
On Jan 7, 2008 6:32 PM, Dan Kegel <da...@ke...> wrote: > > Y'know, it might be more productive for > you get simply use valgrind on wine. > > That solves the problem of instrumenting Windows binaries. What I need is to support people using Windows as their development machine. I'm mostly interested in running custom skins on Windows; people using Windows normally buy functionality similar to that of memcheck already. It sure is more practical to have wine deal with Windows syscalls and executable formats, when this works out. For starters, I was thinking about getting "text-only" programs to work (basically those only relying on the standard C library to talk to the OS). That would be very useful to me; I don't know whether it's very useful in general. -- Yossi |