Eric Pouech writes:
> Uwe Bonnes wrote:
> >
> > Hallo,
> >
> > probably another silly question, but can we compile winedbg as a win32
> > executable and run it in windows? Or is there another free windows
> > debugger, prefered controlled by typing and not clicking?
>
> I've tried to make WineDBG as close as possible to a win32 app
> however, I'm not sure all the unix-isms have been removed (and never
> really tried to compile it under windows). but that should be a goal
>
Hallo,
in a first attempt, I see following problems problems in the code:
Usage of GetCurrentTask: Only available in win16
Usage of GetExePtr: Not exported by name
Usage of wsnprintfA: No Windows API
Usage of mmap/munmap: unix-isms
Usage of vsnprintf: Only _vsnprintf isavaliable as Windows header
Usage of kill: unix-isms
However I think the biggest problems is the inclusion of the right
headers. Most our header files e.g. refer to
#include "ntdef.h"
and while compiling windows source for winelib, this resoulves
fine. However when crosscompiling some of the winelib examples, like
winedbg, this will clash with the crosscompiler supplied system headers
and the wine header. And winedbg at least needs some wine supplied
headers, like module.h.
Has anybody an idea how to solve that?
Bye
Uwe Bonnes [EMAIL PROTECTED]
Free Software: If you contribute nothing, expect nothing
--
