WinDbg quick tip

NTDEV
1

Hi All,

I’ve just downloaded WinDbg v2.0.0023 a few days back, and I’m very
happy
with it as several bugs from prior releases have been fixed - specially
one that
often kept me desperate as the host/target machines wouldn’t synchronize
at all
without a .resync command… it’s working fine now, and kernel-mode
driver
debugging is much reliable… :slight_smile:

What I need from you guys is just a quick tip on a couple of messages
I’m
getting from WinDbg when I reboot my target machine and initiate a
kernel
debug session. Maybe it’s a silly question - probably… I’m novice to
this stuff,
u know… :wink: - but I’m worried about the kind of “information” that
follows, as
I’m not sure whether I’m missing something here…

When I start a debug session, WinDbg comes up with the usual stuff:

Opened \.\COM1

Microsoft (R) Windows Kernel Debugger
Version 2.0.0023.0
Copyright (C) Microsoft Corporation. 1981-2001

Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
(…)
Windows 2000 Kernel Version 2195 MP (1 procs) Checked x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x804dcb80
(…)

Everything’s fine here - it goes on normally (I guess) except for these
next messages:

(…)
740.736p> Cairole: Leaked 2292 bytes (23 allocations)
740.736p> heap: ***** 2292 bytes leaked mem for CDebugMalloc in
‘“C:\WINNT\System32\mobsync.exe” /logon’
[TrkWks/123256.182:100] Couldn’t sync with server (0x8007054b)
420.816p> Cairole: Unbalanced call to CoInitialize for thread 816
(…)
724.112p> Cairole: Leaked 604 bytes (7 allocations)
724.112p> heap: ***** 604 bytes leaked mem for CDebugMalloc in
‘mobsync.exe /logoff’
(…)

When I shutdown the target machine, this message also comes up:

(…)
***** 652 bytes leaked mem for CDebugMalloc in
‘C:\WINNT\system32\MSTask.exe’
(…)

My (silly?) questions are:

  1. Are these “memory leakings” usual, or is there something wrong here?
  2. What’s the purpose of the ‘mobsync.exe’ application? Am I right to
    guess it has something to do
    with my previous “bad experiences” trying to synchronize both
    host/target machines? If the
    answer is yes, then WinDbg is (apparently) overriding the “bug” and
    working fine; however, is
    there something I can/should do about it?
  3. The MSTask.exe “leaked mem” at shutdown is somewhat related to the
    above issues? If not,
    what’s going on here? What seems to be the problem with
    CDebugMalloc?..

Any enlightment here would be most appreciated… Thank you. :wink:

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Miguel,

Welcome to the world of Windows device driver development. What you are
seeing are (some of) the bugs in the Checked build of Windows 2000. As
surprising as it may be to you, there are some bugs that got left in when
Windows 2000 was frozen and shipped. You won’t see those messages if you
connect your debugger to the Free build, because all the DbgPrints end up
being compiled out. No way to tell if the bugs are still there. :slight_smile:

I’m not absolutely sure, but I don’t think mobsync has anything to do with
the debugger.

Phil

-----Original Message-----
From: Miguel Monteiro [mailto:xxxxx@criticalsoftware.com]
Sent: Monday, March 05, 2001 5:25 AM
To: NT Developers Interest List
Subject: [ntdev] WinDbg quick tip

Hi All,

I’ve just downloaded WinDbg v2.0.0023 a few days back, and I’m very
happy
with it as several bugs from prior releases have been fixed - specially
one that
often kept me desperate as the host/target machines wouldn’t synchronize
at all
without a .resync command… it’s working fine now, and kernel-mode
driver
debugging is much reliable… :slight_smile:

What I need from you guys is just a quick tip on a couple of messages
I’m
getting from WinDbg when I reboot my target machine and initiate a
kernel
debug session. Maybe it’s a silly question - probably… I’m novice to
this stuff,
u know… :wink: - but I’m worried about the kind of “information” that
follows, as
I’m not sure whether I’m missing something here…

When I start a debug session, WinDbg comes up with the usual stuff:

Opened \.\COM1

Microsoft (R) Windows Kernel Debugger
Version 2.0.0023.0
Copyright (C) Microsoft Corporation. 1981-2001

Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
(…)
Windows 2000 Kernel Version 2195 MP (1 procs) Checked x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x804dcb80
(…)

Everything’s fine here - it goes on normally (I guess) except for these
next messages:

(…)
740.736p> Cairole: Leaked 2292 bytes (23 allocations)
740.736p> heap: ***** 2292 bytes leaked mem for CDebugMalloc in
‘“C:\WINNT\System32\mobsync.exe” /logon’
[TrkWks/123256.182:100] Couldn’t sync with server (0x8007054b)
420.816p> Cairole: Unbalanced call to CoInitialize for thread 816
(…)
724.112p> Cairole: Leaked 604 bytes (7 allocations)
724.112p> heap: ***** 604 bytes leaked mem for CDebugMalloc in
‘mobsync.exe /logoff’
(…)

When I shutdown the target machine, this message also comes up:

(…)
***** 652 bytes leaked mem for CDebugMalloc in
‘C:\WINNT\system32\MSTask.exe’
(…)

My (silly?) questions are:

  1. Are these “memory leakings” usual, or is there something wrong here?
  2. What’s the purpose of the ‘mobsync.exe’ application? Am I right to
    guess it has something to do
    with my previous “bad experiences” trying to synchronize both
    host/target machines? If the
    answer is yes, then WinDbg is (apparently) overriding the “bug” and
    working fine; however, is
    there something I can/should do about it?
  3. The MSTask.exe “leaked mem” at shutdown is somewhat related to the
    above issues? If not,
    what’s going on here? What seems to be the problem with
    CDebugMalloc?..

Any enlightment here would be most appreciated… Thank you. :wink:

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

?Humour and love are God’s answers
to Human weaknesses?

You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com