Re: [ros-dev] I can't debug CoInitialize function

[Thomas Faber]

On 2016-06-09 12:20, Yonggang Chen wrote:
>   After building ReactOS and Rostests successfully, I
> can't debug CoInitialize
>  function through Visual Studio 2015. It seems Visual Studio thinks I'm using
>  their CoInitialize of Windows kernel. 
That's because you _are_ using Windows's version! :)
The "normal" way to debug ReactOS code is on ReactOS, using a kernel
debugger.
However there are a couple tricks that could allow you to use ROS
ole32.dll on Windows. DLL redirection doesn't work for some DLLs
though, as Windows forces the use of its own version for security
reasons.
For dlls where it does work (not sure of ole32 is on the list), one way
is to create a yourapplication.exe.local file next to your executable
and copy the dll into that same directory as well.
https://blogs.msdn.microsoft.com/junfeng/2006/01/24/dotlocal-local-dll-redi…
has some information on the subject.

Best,
Thomas


>   Anybody can help me?
>  
>   
>  
>  Here is the steps I used to compile ReactOS and Rostests:
>  
>  1.       install Build Environment
>  
>  https://reactos.org/wiki/ReactOS_Build_Environment
>  
>   
>  
>  2. download code to the folder specified when by RosBE during installing
>  
>       code: svn://svn.reactos.org/reactos/trunk/reactos
>  
>    http://svn.reactos.org/reactos/trunk/rostests/
>  
>   
>  
>    reactOS directory -> E:\Work\reactos
>  
>    rostests directory -> E:\Work\reactos\modules\rostests
>  
>   
>  
>   
>  
>  3. generate reactos.sln for Visual Stdio
>  
>       (a). Open a Windows DDK/WDK/Visual Studio 2015 command prompt.
>  
>       (b). run the following command in the code root:
>  
>                 configure.cmd VSSolution
>  
>  4. build the huge solutions
>  
>       msbuild reactos.sln /m
>  
>  5. open the 'ole32_winetest.vcxproj'
>  (E:\Work\reactos\output-VS-i386\modules\rostests\winetests\ole32)
>  
>         Set the command arguments 'ole2', set breakpoint at CoInitialize
>  line, and start beginning by pressing F5, but Visual Studio can't get into
>  CoInitialize funtion