K'VO E T'VA BE???

Abe ei tui 4udo deto za 6e go vidite k'vo e:

First-chance exception in CityEngine Sample.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.

Poqvqva se kogata edin try/catch hvane gre6ka!

tursi na google "0xE06D7363", ili wuw MSDN-a

eto ot moja lokalen "MSDN" (ako imash VSNET instaliran) - ms-help://MS.VSCC/MS.MSDNVS/kbwin32/Source/win32sdk/q185294.htm

-------------------------------

Knowledge Base Articles

PRB: Exception Code 0xE06D7363 When Calling Win32 SEH APIs

Q185294


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Visual C++, 32-bit Editions, version 5.0
Microsoft Win32 Application Programming Interface (API), used with:
Microsoft Windows 95
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Workstation version 4.0
the operating system: Microsoft Windows 2000

--------------------------------------------------------------------------------


SYMPTOMS
When you call Win32 Structured Exception Handling (SEH) APIs, such as GetExceptionCode() and GetExceptionInformation(), sometimes the system reports the following exception code:

0xE06D7363
Sometimes GetLastError() also returns this value. This exception code will be used for any error that is raised by the Microsoft Visual C++ compiler through a call to "throw".



CAUSE
All Visual C++ exceptions thrown from code generated by the Microsoft Visual C++ compiler contain this error code. Because this is a compiler- generated error, the code is not listed in the Win32 API header files. The code is actually a cryptic mnemonic device, with the initial "E" standing for "exception" and the final 3 bytes (0x6D7363) representing the ASCII values of "msc".



RESOLUTION
To properly handle the error, you need to wrap the offending code in a try...catch block. This allows the developer to identify the actual Visual C++ exception that was thrown.

While debugging an application with Microsoft Visual Studio, you can halt the program immediately when this exception occurs, before any handler code is invoked. This gives you a chance to view the offending statement and fix the exception yourself by modifying the variable contents, thereby avoiding an unwind. To set how the debugger handles this exception, follow these steps:



Start debugging your application.


From the Debug menu, click Exceptions.


Within the Exceptions dialog box, select error 0xE06D7363.


Change the value of Action from Stop if not handled to Stop always.


P.S. I prestani da puskash topitzi sus nejasni zaglavia!

Samo mi kajete tova opasno li e(moje li da se prenebregne) ili trqbva ne6to da se napravi po vuprosa.Dokolkoto razbiram tova e ne6to kato informaziq,4e nekuv si exeption e bil hvanat ot catch(...) ne znam si kude.Taka li e???