process-explorer

x64 .NET compilation / Process Explorer oddity

谁说胖子不能爱 提交于 2020-01-03 14:43:29
问题 Apologies if any of what I'm about to say makes no sense or overlooks something obvious - my knowledge of CLR internals is spotty. If I understand correctly, then if I just build a solution for 'AnyCPU' in VS2K5 (or point MSBuild at that .sln file with those settings) then the binaries only compile as far as MSIL. They then get JITted to 32-bit if executed on a 32-bit platform or 64-bit code if executed on x64...right? The DLLs are used for a web app and hosted in the W3WP.exe process.

Finding current directory during Visual Studio debugging session?

南笙酒味 提交于 2019-12-18 04:33:29
问题 How can I find the current directory for a .NET application running under the Visual Studio debugger? Update 1 . To be clear: I don't want to change the code or get information in the program itself - I just want to get information about the application currently being debugged. While debugging a .NET Windows Forms application (mixed VB.NET and C#) I was not sure from which location a XML file was being read from. I expected the current directory to be the application's directory. However,

Debugging RtlUserThreadStart in Process Explorer

眉间皱痕 提交于 2019-12-10 16:38:16
问题 I have a multi-threaded wpf application built on 3.5. When I look at the running threads through Process Explorer I see 8 threads all with the same start address, ntdll.dll!RtlUserThreadStart and all eight have a CPU value from 3-6+ and have a high Cycles Delta. I can't figure out what these threads are doing. It is always the same threads. It never varies within the same instance of the application. When I debug my application at the same time and pause the debugger, all these threads are