Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Windos
win32.3rdparty
win32.directx.audio
win32.directx.ddk
win32.directx.graphics
win32.directx.input
win32.directx.managed
win32.directx.misc
win32.directx.networking
win32.directx.sdk
win32.directx.video
win32.dirx.grap.shaders
win32.gdi
win32.international
win32.kernel
win32.messaging
win32.mmedia
win32.networks
win32.ole
win32.rtc
win32.tapi
win32.tapi.beta
win32.tools
win32.ui
win32.wince
win32.wmi
windows.mediacenter
winfx.aero
winfx.announcements
winfx.avalon
winfx.collaboration
winfx.fundamentals
winfx.general
winfx.indigo
winfx.sdk
winfx.winfs
  
 
date: Wed, 28 Feb 2007 22:12:00 -0800,    group: microsoft.public.win32.programmer.tools        back       


Follow up: Has anybody seen the MFC bug before?   
This title is follow-up of "AppVerifier and WinDbg with VB6 are killing me"
http://msdn.microsoft.com/newsgroups/managed/default.aspx?&guid=&sloc=en-us&dg=microsoft.public.win32.programmer.tools&p=1&tid=d5437651-e83d-460c-9316-1bf55e933ecd

Thanks to Prasad, I learned that error was caused by the bug in MFC. I 
reported this to the gentleman in VeriTest. But he replied, "Considering the 
sheer number of 
tests that we conduct on XP, I cant imagine that we would have a critical 
error caused by a bug on that platform."

Has anybody seen this kind of MFC bug before? Is this bug catchable by VB6? 
I really cannot figure out how to catch this error.  Anybody can help? 

Thanks for your help.

Jianke
date: Wed, 28 Feb 2007 22:12:00 -0800   author:   Jianke

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us