Thank you guys. I will try VirtualBox firstly. On 1/31/11, Olaf Siejka <[email protected]> wrote: > Last time i tried WinDBG, it was not possible to determine process which was > using the memory location given in backtrace. Missing MM functionality. Can > provide bug number to anyone interested. > > > Regards > > 2011/1/30 Timo Kreuzer <[email protected]> > >> Hi, >> >> In theory you can also use winDbg for debugging. You need to compile >> reactos with KDBG = 0 and _WINKD_ = 1 >> Then you need a connection between WinDbg and kdcom. You can use com0com >> and map the VM serial port to one >> end of the pair and connect winDbg to the other. This works quite well >> with >> qemu and VBox. >> after WinDbg is connected you should be able to do the basic stuff, like >> stepping, viewing and changing registers, dumping memory. What not works >> is >> attaching to processes, as WinDbg needs symbols for that. so you would >> need >> to compile with MSVC, which is work in progress. This currently limits its >> usability quite a lot. >> >> I used it only on x64, so I can't say how good it works on x86. But afaik >> it works quite well, except that connecting can be a little tricky in the >> beginning. >> >> Timo >> >> >> _______________________________________________ >> Ros-dev mailing list >> [email protected] >> http://www.reactos.org/mailman/listinfo/ros-dev >> >
_______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
