[MonoDevelop] Debugging under Windows (MonoDevelop 2.6 Beta1)

[alex]

Thanks

debugger started. seems to me work ok

10.03.2011, 14:55, "Lluis Sanchez Gual" <slluis.devel at gmail.com>:
> I think I fixed the problem. Please try the latest Windows build from:
>
> http://monodevelop.com/Download/Trunk_Builds
>
> El dj 10 de 03 de 2011 a les 13:14 +0300, en/na alex va escriure:
>
>>  I lightly confused I found two combo boxes for setup platform in Option -> Build -> Compiler tab.
>>
>>  the first of  them is Configuration (Debug/Release) combo box and Platform Combo box (upper of form)
>>  the second of them is Target platform combo box in General option
>>
>>  What is different between these options?
>>
>>  My solution contains two projects
>>
>>  1. CLI (command Line Interface) module - that should be compiled to EXE module
>>  2. Engine module that should be compiled to DLL module
>>
>>  I observed  for exe module
>>   in Platform combo box only x86 option
>>   in Target Platform 4 options (Any CPU,  x86, x64, Itanium)
>>
>>  for DLL module
>>   in Platform combo box only AnyCPU
>>   for target platform 4 options (Any CPU,  x86, x64, Itanium)
>>
>>  Why Platform combo box  contains different alternatives for EXE and DLL?
>>  I've setup x86 for target platform, for EXE and DLL, the rebuilt solution and have the same issue, debugger does not start
>>  I've tried the following scenario : Clean All, then Build All and have the same result, debugger does not start
>>  I've tried the following scenario : Clean All, then ReBuild All and have the same result, debugger does not start
>>
>>  Shall I send additional files, logs etc?
>>
>>  Host OS is Windows XP SP3. OS start as guest OS on VmWare 6.5.1 virtual machine
>>
>>  Thanks
>>  Alex
>>
>>  10.03.2011, 11:28, "Lluis Sanchez Gual" <slluis.devel at gmail.com>;;;:
>>>    The debugger only supports 32bit applications. Make sure you have x86 as
>>>    target platform, and not AnyCPU.
>>>
>>>    El dj 10 de 03 de 2011 a les 11:16 +0300, en/na alex va escriure:
>>>>     Hello
>>>>
>>>>     I tried to use debugger on my project and observed the following.
>>>>     The same result I observed on stable version 2.4.2
>>>>     Seems to me I use wrong options for building. Could you please help me?
>>>>
>>>>     ---------------------- LOG ------------------------------------
>>>>     The debugger's protocol is incompatible with the debuggee. (Exception from HRESULT: 0x8013134B).
>>>>
>>>>     System.Runtime.InteropServices.COMException (0x8013134B): The debugger's protocol is incompatible with the debuggee. (Exception from HRESULT: 0x8013134B)
>>>>        at Microsoft.Samples.Debugging.CorDebug.NativeApi.ICorDebug.CreateProcess(String lpApplicationName, String lpCommandLine, SECURITY_ATTRIBUTES lpProcessAttributes, SECURITY_ATTRIBUTES lpThreadAttributes, Int32 bInheritHandles, UInt32 dwCreationFlags, IntPtr lpEnvironment, String lpCurrentDirectory, STARTUPINFO lpStartupInfo, PROCESS_INFORMATION lpProcessInformation, CorDebugCreateProcessFlags debuggingFlags, ICorDebugProcess& ppProcess)
>>>>        at Microsoft.Samples.Debugging.CorDebug.CorDebugger.CreateProcess(String applicationName, String commandLine, SECURITY_ATTRIBUTES processAttributes, SECURITY_ATTRIBUTES threadAttributes, Boolean inheritHandles, Int32 creationFlags, IntPtr environment, String currentDirectory, STARTUPINFO startupInfo, PROCESS_INFORMATION& processInformation, CorDebugCreateProcessFlags debuggingFlags)
>>>>        at Microsoft.Samples.Debugging.CorDebug.CorDebugger.CreateProcess(String applicationName, String commandLine, String currentDirectory, IDictionary`2 environment, Int32 flags)
>>>>        at MonoDevelop.Debugger.Win32.CorDebuggerSession.OnRun(DebuggerStartInfo startInfo)
>>>>        at Mono.Debugging.Client.DebuggerSession.<>c__DisplayClassc.<Run>b__a()
>>  --
>>  With Best Regards
>>  Alex

-- 
With Best Regards
Alex