On Monday, March 05, 2001 7:39 PM “Barila, Phil” wrote:
Try running mobsync.exe (…). It has absolutely nothing to do with the
sync problems you had using the old versions of WinDBG. (…) The fact
that it’s name has ‘sync’ in it, and you had synchronization issues is
incidental.
Thanx Phil. 
I had no clue what mobsync’s purpose was.
CDebugMalloc is a function in the debug version of the MFC library.
Since
the entire checked build of the OS is a “debug” version, it’s not
surprising
that it gets called.
Of course. That is clear to me; I just misunderstood the function’s
location
(I knew that function had a MFC implementation, but I thought it was a
wrapper for the “real” CDebugMalloc function lying beneath the O.S. or
something… well, we’re always learning… thank’s again).
What is slightly surprising is that the OS, and SP1, shipped while
still
reporting memory leaks. Note to marketing: It’s *really* a good idea
to
fix bugs *that* obvious, before you ship the product.
It’s not that surprising due to the infamous *deadlines*… But I agree
with you
in that *some* bugs are so obvious (like the one mentioned) they
shouldn’t
come up in the wild at all… but hey, we know it isn’t a perfect
world… 
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