Exception in KernelBase

Question

_{Monday, August 5, 2019 11:39 AM}

Debugging this morning and I see a slew of these types of messages

Exception thrown at 0x00007FFDC850A388 (KernelBase.dll) in clicast.exe: 0x20474343 (parameters: 0x00000186EA91C770).

The thing is I have Visual Studio 2017 set up to load symbols from the Microsoft symbol server, but this is not showing where in KernelBase (or our code) where the exception is being thrown.  I can aonly assume it was handled as our application does not crash.

Any ideas would be helpful.

Thanks,

Tom

All replies (5)

_{Tuesday, August 6, 2019 5:40 AM}

Hi Tom,

Welcome to the MSDN forum.

What type of project are you debugging? Did you face this problem before?

According to your description, please check whether your local debugging configuration is the same as  the application configuration such as the platform.

If these do not work, please share some key codes or ActivityLog.xml which collects the detailed information during the process so that we can help you further.

Any feedback will be expected.

Best Regards,

Perry

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

_{Wednesday, August 7, 2019 9:47 AM}

Hi Tom,

Did your issue solved? It seems that you built the application from the other agent and debugged it in your local agent. If so, please check whether the configuration parameter is the same.

If the issue still exists ,please feel free to let us know. 

Best Regards,

Perry

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

_{Wednesday, August 7, 2019 1:22 PM}

Hi,

This is the first time I have tried debugging in Visual Studio 2017, so I am not sure if this existed before or if I am just seeing it now.

I am building from the command line, not from the GUI.  The object code produced would be the equivalent of Release|x64.

I have been trying different things.  I am going to try the debugger again today.

_{Wednesday, August 7, 2019 1:46 PM}

Just because the Visual Studio debugger reports an exception in kernelbase.dll, it doesn't mean that the exception was thrown there or uncaught.

For example:

#include <Windows.h>

int wmain()
{
    __try
    {
        RaiseException(500000, 0, 0, nullptr);
    }
    __except (GetExceptionCode() == 500000 ? EXCEPTION_EXECUTE_HANDLER : EXCEPTION_CONTINUE_SEARCH)
    {

    }
    return 0;
}

will report:

Exception thrown at 0x00007FF848C9A839 (KernelBase.dll) in meh.exe: 0x0007A120.

in the output window. The reported address itself is not really important since ASLR moves kernelbase.dll around in memory, and different versions of kernelbase.dll may start off the exception at different locations.

Notice two important things:

1) The exception was caught yet the debugger still reported it.

2) The exception was thrown using the RaiseException call, and this was in my executable's main function. Yet it reported that it was thrown in KernelBase.dll.

All this message means that an exception was raised but was also handled at some point in your code. You can ignore it.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

_{Friday, August 9, 2019 9:42 AM}

Hi Tom,

Did your issue solved?

If you issue still exists, please try to create a small demo in your VS2017 to test whether your IDE has error.

If you also cannot debug, please reinstall your VS and delete the component cache in this path          >>>>"%LocalAppData%\Microsoft\VisualStudio\15.0_xxx\ComponmentModelCache".

If it can debug the new demo, please make sure that the vs version of developing your project is the same as the vs version of testing the project. Because when versions are inconsistent, projects of the old version need to be recompiled when they are migrated to the new version of VS.

Any feedback will be expected.

Best Regards,

Perry

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]