c++ - CDirScan function NextL raises KERN-EXEC 0 -
The CDirScan function has raised "Main Terror KERN-EXEC 0" if it is not called the correct settings () That is, if it is later called after another event within the same active object)
f1 () - Called within the active object
iDirScan = CDirScan :: NewLC (AFS); IDirScan-> Setscen Datel (Epath, KentriDIR | KentriatMachXil, Easserton, CDIRCan :: Eskendowntree); // Wait for some asynchronous event
f2 () - some of the asynchronous event
CDir * dir = NULL after the same active object Called; TRAPD (error, IDIRSKN-> Next L (DIR)); - & gt; & Gt; "Main Terror Ken-Ecc 0"
If anything is called iDirScan-> NextL () before waiting for an asynchronous event, then everything works fine
< P> Why does the CDirScan variable lose its validity? Note that there is nothing to do for asynchronous event, it can be a simple dummy timer.
I wrote some test codes in an attempt to reproduce it, but could not.
Generally, KERN-EXEC 0
nervousness is often caused by stale R object handles, for example, make sure that RF
is < Code> CDirScan has not been quickly closed.
Comments
Post a Comment