Improve Null Reference Exception handling

[mterwoord]

Right now, visual studio shows a message like:

NullReferenceException occurred at address 0x020B9FBB! Halting now.

whenever a NullReferenceException occurs. This could be improved to show, at least the method name and instruction location it occurs.

[cjhannah]

This would be greatly appreciated.

[jp2masa]

It annoys me too. I'll try to do this.

[ghost]

This is why I'd have a try/catch in my Run() that's a catch-all, and if an exception occurs and isn't handled before it hits Run(), it prints exception message to the console, then your OS just resumes and keeps on going.

On Wed, Sep 14, 2016 at 12:37 PM, jp2masa [email protected] wrote:

It annoys me too. I'll try to do this.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CosmosOS/Cosmos/issues/93#issuecomment-247074620, or mute the thread https://github.com/notifications/unsubscribe-auth/ARf_UFIsAg6OfvuDXHCjVYjoHk50JYDTks5qqCLFgaJpZM4EVksM .

[github-actions[bot]]

As this issue has received no new activity, it has been marked as stale

[JuliusCaesar12]

I have found out that when a Null Reference Exception occurs anywhere, it causes an invalid opcode exception and halts the CPU.

[selkij]

Still happening and still very annoying