By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
If <code>what</code> is 0 or any invalid value, nothing is done.
If <code>what</code> is 0 or any invalid value, nothing is done.
−
If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions. The function handling it reads fields from the faulted or the main thread's TLS and most often writes the data structure on the faulted thread's stack.
+
If it is 1, <code>val != 0</code> is written to the global variable enabling ERR:F-format register dumps on user-mode CPU/VFP exceptions (the VFP exception handler acts as if this variable was always true and works on retail environments). The function handling it reads fields from the faulted or the main thread's TLS and most often writes the data structure on the faulted thread's stack.
If 2, kernelpanic will be called when svcBreak is used by a non-attached process
If 2, kernelpanic will be called when svcBreak is used by a non-attached process