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: Tue, 10 Jun 2008 20:44:00 -0700,    group: microsoft.public.win32.programmer.directx.misc        back       


ETW. CloseTrace does not close a handle. Is it a bug   
I am using Event Trace Window(e.i. ETW) on Windows 2003 to process events in 
real time mode. When an event provider is not running, the function 
ProcessTrace returns the error code 0x1069, which means “The instance name 
passed was not recognized as valid by a WMI data provider”.  
Subsequent call to CloseTrace returns the error code 0xaa, which is “The 
requested resource is in use”, and the handle lefts open. If I ignore this 
error and try to call OpenTrace again, the number of process handles is 
constantly growing. 

Snip of my code:

OpenTrace
while (!End){
    rc  = ProcessTrace
    if (rc) {
        CloseTrace
        OpenTrace
    }
}
CloseTrace

Any suggestions are greatly appreciated
date: Tue, 10 Jun 2008 20:44:00 -0700   author:   Volodymyr Tarasevych Volodymyr

Google
 
Web ureader.com


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