🦠Diagnostics

Trying to find a defect in the kernel? Great! Thanks for your contribution!

The simulated kernel contains its own diagnostic tools to allow you to diagnose what's wrong with a feature. These diagnostic tools help you analyze the kernel for what it's doing and for how it failed.

There are two ways to diagnose the kernel: in-kernel debugging, and using Visual Studio.

In-kernel Debugging

In-kernel debugging allows you to use its own built-in tools to debug the kernel and its components. For more information, head to the below page.

🔬Debugging

Visual Studio

This way of debugging is only available if you have Visual Studio installed. If you have the source code of the kernel cloned from our GitHub, you can attach the Nitrocid KS process to the debugger. Here's how, assuming that Nitrocid KS is already open:

1. Open Visual Studio to the empty project

2. Right-click on Debug -> Attach to Process

3. Find Nitrocid.exe

4. Click on Attach

5. In case Visual Studio is asking for source files, point to a file within the Nitrocid KS source

Please note that we currently don't fully support Source Link, but we're working on it after Beta 3.

KernelException Class

KernelException is an exception class that uses the exception type to give you a possible cause for each exception type. The kernel (and your mods) make extensive use of this exception to signal an error, but this class can also hold an inner exception of either the nested KernelException class or any of the Exception classes.

Each KernelException instance holds the following properties:

• ExceptionType: Specifies the exception type using the KernelExceptionType enumeration.

• OriginalExceptionMessage: Specifies the original exception message before being processed.

• KernelExceptionMessage: Shows a full message from the exception type.