Intel® oneAPI DPC++/C++ Compiler
Talk to fellow users of Intel® oneAPI DPC++/C++ Compiler and companion tools like Intel® oneAPI DPC++ Library, Intel® DPC++ Compatibility Tool, and Intel® Distribution for GDB*

"oneapi-cli.exe" crashes "conhost.exe"

GisleVanem
Beginner
715 Views

Hi all.

 

After downloading and installing the latest 2024.0 version of the oneAPI, I

was glad to see that the directory layout and number of required paths has been

reduced. Seems most EXEs, now have been SYMLINK'ed into %ONEAPI_ROOT%\2024.0\bin.

E.g. F:\gv\Intel\oneAPI> dir 2024.0\bin shows:

24.12.2023 05:48 <DIR> 1033
24.12.2023 05:48 <DIR> compiler
24.12.2023 05:48 <DIR> vc14_uwd
24.12.2023 05:48 <DIR> vc14_uwp
24.12.2023 05:48 <DIR> vc_mt
24.12.2023 05:48 <SYMLINK> git-clang-format [..\..\compiler\2024.0\bin\git-clang-format]
24.12.2023 05:48 <SYMLINK> run-clang-tidy [..\..\compiler\2024.0\bin\run-clang-tidy]
24.12.2023 05:48 <SYMLINK> gdb-oneapi.bat [..\..\debugger\2024.0\bin\gdb-oneapi.bat]
24.12.2023 05:48 <SYMLINK> cl.cfg [..\..\compiler\2024.0\bin\cl.cfg]
24.12.2023 05:48 <SYMLINK> cl.fpga_emu.cfg [..\..\compiler\2024.0\bin\cl.fpga_emu.cfg]
24.12.2023 05:48 <SYMLINK> icpx.cfg [..\..\compiler\2024.0\bin\icpx.cfg]
24.12.2023 05:48 <SYMLINK> icx.cfg [..\..\compiler\2024.0\bin\icx.cfg]
24.12.2023 05:48 <SYMLINK> sycl.conf [..\..\compiler\2024.0\bin\sycl.conf]
24.12.2023 05:48 <SYMLINK> tbb.def [..\..\tbb\2021.11\bin\tbb.def]
24.12.2023 05:48 <SYMLINK> tbbmalloc.def [..\..\tbb\2021.11\bin\tbbmalloc.def]
24.12.2023 05:48 <SYMLINK> common_clang64.dll [..\..\compiler\2024.0\bin\common_clang64.dll]
24.12.2023 05:48 <SYMLINK> crypto_mb.dll [..\..\ippcp\2021.9\bin\crypto_mb.dll]

...

 

But running F:\gv\Intel\oneAPI>2024.0\bin\oneapi-cli.exe in my TCC shell [1], it crashes conhost.exe real good! I do not use a Legacy Console (but ANSI)

[1] https://jpsoft.com/products/tcc.html

These are some details:

Connecting to online Sample Aggregator....  Boom!

WinDbg kicks in with:

ucrtbase!abort+0x4e
ucrtbase!terminate+0x1f
ucrtbase!FindHandler<__FrameHandler4>+0x50a
ucrtbase!__InternalCxxFrameHandler<__FrameHandler4>+0x278
ucrtbase!_CxxFrameHandler4+0xa0
ntdll!RtlpExecuteHandlerForException+0xf
ntdll!RtlDispatchException+0x244
ntdll!RtlRaiseException+0x1d7
KERNELBASE!RaiseException+0x69
ucrtbase!CxxThrowException+0xad
conhost!wil::details::ThrowResultExceptionInternal+0x4e
conhost!wil::details::ReportFailure+0x236aa
conhost!wil::details::ReportFailure_Hr+0x44
conhost!wil::details::in1diag3::Throw_Hr+0x26
conhost!TextBufferCellIterator::TextBufferCellIterator+0x1fca6
conhost!RenderData::IsCursorDoubleWidth+0xd5
conhost!Microsoft::Console::Render::Renderer::_PaintCursor+0xd4
conhost!Microsoft::Console::Render::Renderer::_PaintFrameForEngine+0x1cc
conhost!Microsoft::Console::Render::Renderer::PaintFrame+0x86
conhost!Microsoft::Console::Render::RenderThread::_ThreadProc+0x56
KERNEL32!BaseThreadInitThunk+0x14

And an !analyze -v shows:

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcbb0a286e (ucrtbase!abort+0x000000000000004e)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000007
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT

FAULTING_THREAD: 00003700

PROCESS_NAME: conhost.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - Det ble oppdaget en overflyt i en stakkbasert buffer i programmet. Overflyten kan f re til at ondsinnede brukere tar kontroll over programmet.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000007

CONTEXT: 00000037d467dd90 -- (.cxr 0x37d467dd90)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000148d4ad0000 rdi=00000148d4ad02bc
rip=0000000000000080 rsp=00000148d4ad18c0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000070 r10=00000148d4ad0cc0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000070 r15=0000000000000067
iopl=0 nv up di pl nz na pe nc
cs=ffff ss=0000 ds=ffff es=ffff fs=ffff gs=0000 efl=00000000
00000000`00000080 ?? ???
Resetting default scope

IP_ON_STACK:
+0
00000148`d4ad0cc0 2e0023 add byte ptr cs:[rbx],ah

FRAME_ONE_INVALID: 1

STACK_TEXT:
00000037`d467cc60 00007ffc`bb0a1f9f : 00000037`00000003 00000037`00000003 00007ffc`bb079ee6 00000037`d467cda0 : ucrtbase!abort+0x4e
00000037`d467cc90 00007ffc`bb06ee66 : 00000037`d467def0 00000037`d467d560 00000037`d467def0 00000037`d467cf70 : ucrtbase!terminate+0x1f
00000037`d467ccc0 00007ffc`bb06fae4 : 00000000`00000000 00007ffc`ba970fbb 00000000`00000001 00000037`d467def0 : ucrtbase!FindHandler<__FrameHandler4>+0x50a
00000037`d467ce90 00007ffc`bb06d950 : 00007ff6`65d50000 00000037`d467def0 00000037`d467d720 00000037`d467d560 : ucrtbase!__InternalCxxFrameHandler<__FrameHandler4>+0x278
00000037`d467cf30 00007ffc`bd1723af : 00000037`d467f7f0 00000000`00000000 00000037`d467d510 00000037`d467def0 : ucrtbase!_CxxFrameHandler4+0xa0
00000037`d467cfa0 00007ffc`bd1214b4 : 00000000`00000000 00000037`d467d510 00000037`d467def0 00000000`00000001 : ntdll!RtlpExecuteHandlerForException+0xf
00000037`d467cfd0 00007ffc`bd121207 : 00000000`00000000 00000037`d467dd90 00000000`00000000 00000037`d467d720 : ntdll!RtlDispatchException+0x244
00000037`d467d6e0 00007ffc`ba94cf19 : 00000000`00000000 00007ff6`65e0b798 00000037`d467f848 00000000`00000000 : ntdll!RtlRaiseException+0x1d7
00000037`d467ded0 00007ffc`bb06da1d : 00000148`d755d1a0 00007ff6`65d872f3 00000037`d467e0d0 00000000`0000000c : KERNELBASE!RaiseException+0x69
00000037`d467dfb0 00007ff6`65d8895e : 00007ff6`65d50000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!CxxThrowException+0xad
00000037`d467e020 00007ff6`65d7d136 : 00007ff6`65d5d7b5 00000000`00000000 00000037`d467f789 00000037`d467f848 : conhost!wil::details::ThrowResultExceptionInternal+0x4e
00000037`d467e120 00007ff6`65d59a80 : 00007ffc`bb03f020 00b90000`00b90000 00000037`d467f7c0 00007ff6`65d62217 : conhost!wil::details::ReportFailure+0x236aa
00000037`d467f660 00007ff6`65d8d63a : 00000000`00000d38 00000148`d6f68040 00b90000`00370000 00000000`00000000 : conhost!wil::details::ReportFailure_Hr+0x44
00000037`d467f6c0 00007ff6`65d7f956 : 00000000`00380000 00007ffc`bae39115 00000148`d6f68040 00000000`0000008c : conhost!wil::details::in1diag3::Throw_Hr+0x26
00000037`d467f710 00007ff6`65d5d7b5 : 0037008b`00000000 00000148`d495b940 00000148`23280000 00000000`00000000 : conhost!TextBufferCellIterator::TextBufferCellIterator+0x1fca6
00000037`d467f7f0 00007ff6`65d5af94 : 00000148`d493e000 0037008b`00000000 00000148`d493e060 00000037`d467f8f0 : conhost!RenderData::IsCursorDoubleWidth+0xd5
00000037`d467f8c0 00007ff6`65d5b5dc : 00000148`d493e060 00000000`00000000 00000148`d493e060 00000000`00000000 : conhost!Microsoft::Console::Render::Renderer::_PaintCursor+0xd4
00000037`d467f940 00007ff6`65d5b3e6 : 00000000`00000000 00007ffc`ba98b8bb 00000000`00000000 00000000`00000003 : conhost!Microsoft::Console::Render::Renderer::_PaintFrameForEngine+0x1cc
00000037`d467fa20 00007ff6`65d6b7ca : 00000148`d495f3e0 00000000`00000000 00000000`00000000 00000000`00000000 : conhost!Microsoft::Console::Render::Renderer::PaintFrame+0x86
00000037`d467fa60 00007ffc`bcfe7344 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : conhost!Microsoft::Console::Render::RenderThread::_ThreadProc+0x56
00000037`d467fa90 00007ffc`bd1226b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
00000037`d467fac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


STACK_COMMAND: ~1s ; .cxr ; kb

SYMBOL_NAME: ucrtbase!abort+4e

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.3636

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

Followup: MachineOwner
---------

 

I see this call-stack in another non-crashing thread:

ntdll!NtWaitForAlertByThreadId+0x14
ntdll!RtlpWaitOnAddressWithTimeout+0x81
ntdll!RtlpWaitOnAddress+0xae
ntdll!RtlpWaitOnCriticalSection+0xfd
ntdll!RtlpEnterCriticalSectionContended+0x1c4
ntdll!RtlEnterCriticalSection+0x42
conhost!Microsoft::Console::Interactivity::Win32::Window::ConsoleWindowProc+0x68
conhost!Microsoft::Console::Interactivity::Win32::Window::s_ConsoleWindowProc+0x53
user32!UserCallWinProcCheckWow+0x2f8
user32!DispatchClientMessage+0x9c
user32!_fnDWORD+0x33
ntdll!KiUserCallbackDispatcherContinue
win32u!NtUserGetMessage+0x14
user32!GetMessageW+0x2e
conhost!ConsoleInputThreadProcWin32+0x75
KERNEL32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21

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

 

No issue running oneapi-cli.exe from cmd.exe, but yuk!

 

To recover, I exit WinDbg. But the parent shell tcc.exe is stuck w/o a conhost.exe attached. 

I have to use ProcessExplorer to kill the tcc.exe + oneapi-cli.exe tree. At this point oneapi-cli.exe has 15 active threads.

 

Anybody who has an idea of what the heck is going on here?

 

 

0 Kudos
1 Reply
Alex_Y_Intel
Moderator
600 Views

Hi @GisleVanem 
Thanks for posting your question in the forum. Can you please provide a reproducer to demonstrate your issue and list clearly the reproducing steps? 

0 Kudos
Reply