DebugDiag not working in amd64 Windows 2003

[Robertis Tongbram]

i all,

I'm trying to use Debug Diag to monitor memory leaks in 64-bit windows 2003
amd64.

And when i try ot attach the process, it says :

GetLastError returns 0x00000005. Could not monitor for leaks in process id
<PID>.

I downloaded DebugDiag from:

http://www.microsoft.com/downloads/details.aspx?familyid=7E42B310-B2D1-496B-8005-9D91782B9995&displaylang=en

PS : i use it a lot in x86 and it works perfectly.
Any idea?

Thanks,
Robertis

[Tiago Halm]

I'd say the GetLastError 0x5 is an Access Denied. Have you ran
Filemon/Regmon?

Tiago Halm

"Robertis Tongbram" <Robertis...@discussions.microsoft.com> wrote in
message news:0287129B-F988-4283...@microsoft.com...

[Robertis Tongbram]

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.

[David Wang]

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).

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

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?
>
> > Tiago Halm
>

> > "Robertis Tongbram" <RobertisTongb...@discussions.microsoft.com> wrote in
> > messagenews:0287129B-F988-4283...@microsoft.com...

> > >i all,
>
> > > I'm trying to use Debug Diag to monitor memory leaks in 64-bit windows
> > > 2003
> > > amd64.
>
> > > And when i try ot attach the process, it says :
>
> > > GetLastError returns 0x00000005. Could not monitor for leaks in process id
> > > <PID>.
>
> > > I downloaded DebugDiag from:
>

> > >http://www.microsoft.com/downloads/details.aspx?familyid=7E42B310-B2D...

>
> > > PS : i use it a lot in x86 and it works perfectly.
> > > Any idea?
>
> > > Thanks,

> > > Robertis- Hide quoted text -
>
> - Show quoted text -

[Robertis Tongbram]

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:

> > > >http://www.microsoft.com/downloads/details.aspx?familyid=7E42B310-B2D....

[David Wang]

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.

Hope this helps.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

On Mar 12, 10:57 am, Robertis Tongbram

> > > - Show quoted text -- Hide quoted text -

[Robertis Tongbram]

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]

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.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

On Mar 12, 1:03 pm, Robertis Tongbram

> > //- Hide quoted text -