DebugDiag is currently 32bit only. There's no native x64 product (yet)
We published it as part of the IIS Diagnostics Toolkit (x64) because you can use it to debug WOW64 processes on x64, on top of just plain 32bit applications on 32bit OS.
However, it hardly prevents one from debugging on x64. Windows Debugging Tools are perfectly capable of doing the same (in fact, DebugDiag uses the same Debugger Engine).
<RobertisTongb...@discussions.microsoft.com> wrote: > No. I didnt run that. > In x86 I didnt have to run run that. > I expect the amd64 version to work on amd64. > I tried in 3/4 machines. None worked.
> "Tiago Halm" wrote: > > I'd say the GetLastError 0x5 is an Access Denied. Have you ran > > Filemon/Regmon?
Thanks David. It made things clear, except for "However, it hardly prevents one from debugging on x64."
Does it mean there are other debugging tools I can use for monitoring leaks for native x64 processes ( not WOW64 )? I tried Leakdiag too, it doesn't work.
WinDbg works perfectly fine though, but I'm looking for something that detects leaks as good as DebugDiag.
"David Wang" wrote: > DebugDiag is currently 32bit only. There's no native x64 product (yet)
> We published it as part of the IIS Diagnostics Toolkit (x64) because > you can use it to debug WOW64 processes on x64, on top of just plain > 32bit applications on 32bit OS.
> However, it hardly prevents one from debugging on x64. Windows > Debugging Tools are perfectly capable of doing the same (in fact, > DebugDiag uses the same Debugger Engine).
> On Mar 11, 6:54 pm, Robertis Tongbram > <RobertisTongb...@discussions.microsoft.com> wrote: > > No. I didnt run that. > > In x86 I didnt have to run run that. > > I expect the amd64 version to work on amd64. > > I tried in 3/4 machines. None worked.
> > "Tiago Halm" wrote: > > > I'd say the GetLastError 0x5 is an Access Denied. Have you ran > > > Filemon/Regmon?
Leak detection (and just about anything else) can be done with any of those debuggers, including WinDbg, if you know the right commands and what to look for. Developers at Microsoft use those same tools to track down memory leaks, and DebugDiag/TraceDiag uses the same things as well.
DebugDiag/LeakDiag was the culmination of a lot of experienced debuggers/programmers, a huge customer need on 32bit x86 machines. Need on 64bit x64 machines isn't quite there yet, but I suspect someday it will be.
So, the real issue is that you need a tool on 64bit that knows the right commands and what to look for, but it does not exist yet (because the business need hasn't arisen yet).
If you need the problem solved now, you will probably have to find someone to do it, pay someone like Microsoft PSS to look at it, or learn how to do it yourself.
And probably lodge a feature request to Microsoft PSS for a 64bit DebugDiag.
Sorry that it doesn't help you now, but I wanted to make sure that you can contribute to forward progress.
<RobertisTongb...@discussions.microsoft.com> wrote: > Thanks David. It made things clear, except for > "However, it hardly prevents one from debugging on x64."
> Does it mean there are other debugging tools I can use for monitoring leaks > for native x64 processes ( not WOW64 )? I tried Leakdiag too, it doesn't work.
> WinDbg works perfectly fine though, but I'm looking for something that > detects leaks as good as DebugDiag.
> Thanks, > Robertis
> "David Wang" wrote: > > DebugDiag is currently 32bit only. There's no native x64 product (yet)
> > We published it as part of the IIS Diagnostics Toolkit (x64) because > > you can use it to debug WOW64 processes on x64, on top of just plain > > 32bit applications on 32bit OS.
> > However, it hardly prevents one from debugging on x64. Windows > > Debugging Tools are perfectly capable of doing the same (in fact, > > DebugDiag uses the same Debugger Engine).
> > On Mar 11, 6:54 pm, Robertis Tongbram > > <RobertisTongb...@discussions.microsoft.com> wrote: > > > No. I didnt run that. > > > In x86 I didnt have to run run that. > > > I expect the amd64 version to work on amd64. > > > I tried in 3/4 machines. None worked.
> > > "Tiago Halm" wrote: > > > > I'd say the GetLastError 0x5 is an Access Denied. Have you ran > > > > Filemon/Regmon?
Thanks a lot. It seems like I need to look deeper into WinDbg. Or probably build one x86 version and debug it there. DebugDiag was just too easy and comfortable to switch to something else :) .
"David Wang" wrote: > Leak detection (and just about anything else) can be done with any of > those debuggers, including WinDbg, if you know the right commands and > what to look for. Developers at Microsoft use those same tools to > track down memory leaks, and DebugDiag/TraceDiag uses the same things > as well.
> DebugDiag/LeakDiag was the culmination of a lot of experienced > debuggers/programmers, a huge customer need on 32bit x86 machines. > Need on 64bit x64 machines isn't quite there yet, but I suspect > someday it will be.
> So, the real issue is that you need a tool on 64bit that knows the > right commands and what to look for, but it does not exist yet > (because the business need hasn't arisen yet).
> If you need the problem solved now, you will probably have to find > someone to do it, pay someone like Microsoft PSS to look at it, or > learn how to do it yourself.
> And probably lodge a feature request to Microsoft PSS for a 64bit > DebugDiag.
> Sorry that it doesn't help you now, but I wanted to make sure that you > can contribute to forward progress.
Yes, I agree. Looking into WinDbg has lots of long-term benefits.
The comforts simply lull one into complacency. Personally, I find DebugDiag very limiting. It can be nice at automating some of the things I do by hand, but leaks, crashes, and hangs are very common and very methodical and straight-forward to diagnose (hence we can craft a tool to automate).
Of course, I recognize that Debug has its place and target audience -- I don't fit the audience -- but I always advocate people who can debug to do some and improve because it bestows so many benefits.
<RobertisTongb...@discussions.microsoft.com> wrote: > Thanks a lot. It seems like I need to look deeper into WinDbg. > Or probably build one x86 version and debug it there. > DebugDiag was just too easy and comfortable to switch to something else :) .
> Thanks, > Robertis
> "David Wang" wrote: > > Leak detection (and just about anything else) can be done with any of > > those debuggers, including WinDbg, if you know the right commands and > > what to look for. Developers at Microsoft use those same tools to > > track down memory leaks, and DebugDiag/TraceDiag uses the same things > > as well.
> > DebugDiag/LeakDiag was the culmination of a lot of experienced > > debuggers/programmers, a huge customer need on 32bit x86 machines. > > Need on 64bit x64 machines isn't quite there yet, but I suspect > > someday it will be.
> > So, the real issue is that you need a tool on 64bit that knows the > > right commands and what to look for, but it does not exist yet > > (because the business need hasn't arisen yet).
> > If you need the problem solved now, you will probably have to find > > someone to do it, pay someone like Microsoft PSS to look at it, or > > learn how to do it yourself.
> > And probably lodge a feature request to Microsoft PSS for a 64bit > > DebugDiag.
> > Sorry that it doesn't help you now, but I wanted to make sure that you > > can contribute to forward progress.
