Sign in
Microsoft.com
 
Microsoft
 
 
 

none
not spam RRS feed

 , 
 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are developing a product on the following Intel processor:  Intel Apollo lake N4200.  This is released silicon.  When using a core i7 on the target we can remote debug without issue.  When we have the Intel Apollo Lake on the target we get the below error message: 

    The remote debugger has encountered a serious internal error, and must abort the remote debugging session.  Please restart the debugger.

    We have tried both an commercially available consumer grade motherboard from ASROCK.  We have also tried our commercial grade COM-E module with the same result.

    This happens with our WPF application when native debugging is checked.  We do not see this issue with MFC applications.

    Below are the stack traces:

    Windows 10 Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    Built by: 10.0.14393.0 (rs1_release.160715-1616)
    Machine Name:
    Debug session time: Thu Mar 16 16:20:34.000 2017 (UTC - 7:00)
    System Uptime: 0 days 1:20:09.160
    Process Uptime: 0 days 0:01:22.000
    ................................................................
    ...............................
    Loading unloaded module list
    ....
    ntdll!NtWaitForSingleObject+0x14:
    00007ffb`98ca4ed4 c3              ret
    0:000> kb
    RetAddr           : Args to Child                                                           : Call Site
    00007ffb`952175ff : 00000000`000001d8 00000000`00000000 00000000`00000000 00000000`00000003 : ntdll!NtWaitForSingleObject+0x14
    00007ff7`d08d10fe : 00000039`1bd0f3e0 00000039`1bd0f308 00000000`00000000 00000000`00000178 : KERNELBASE!WaitForSingleObjectEx+0x8f
    00007ff7`d08d106f : 00000000`00000000 00000000`00000000 00000000`00000000 000001f7`5e5c4670 : msvsmon!msvsmon::CRootServer::WaitForExitProcess+0x3cd
    00007ff7`d08d11ce : 00000039`1bd0f3e0 00000039`1bd0f6a0 00000039`1bd0f3e0 00000039`1bd0f3e0 : msvsmon!msvsmon::CRootServer::MainThreadFunction+0x17
    00007ff7`d08d1aeb : 00000000`00000000 00000039`1bd0f780 00000000`00000001 00000039`1bd0f6a0 : msvsmon!msvsmon::CRootServer::Run+0x146
    00007ff7`d08d1a33 : 00000000`00000000 00000000`00000000 000001f7`5e5720c4 00000000`00000000 : msvsmon!msvsmon::CRootServer::Main+0xa7
    00007ff7`d09365d6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!WinMain+0x255
    00007ffb`96638364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!__scrt_common_main_seh+0x11e
    00007ffb`98c65e91 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
    00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

    Also the second stack:

    Windows 10 Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    Built by: 10.0.14393.0 (rs1_release.160715-1616)
    Machine Name:
    Debug session time: Thu Mar 16 16:20:43.000 2017 (UTC - 7:00)
    System Uptime: 0 days 1:20:18.255
    Process Uptime: 0 days 0:01:31.000
    ................................................................
    ...........
    Loading unloaded module list
    .
    ntdll!NtWaitForMultipleObjects+0x14:
    00007ffb`98ca59a4 c3              ret
    0:000> kb
    RetAddr           : Args to Child                                                           : Call Site
    00007ffb`9524c19f : 0000022a`00000014 00000000`0000000a 00000000`00000000 00000000`00000100 : ntdll!NtWaitForMultipleObjects+0x14
    00007ffb`98516f54 : 0000022a`7c504be0 000000c5`00000000 00000000`00000000 00000000`00000001 : KERNELBASE!WaitForMultipleObjectsEx+0xef
    00007ffb`98516dd5 : 00000000`00000000 000000c5`eb0ff518 00000000`00000001 000000c5`eb0ff510 : combase!DefaultWaitForHandles+0x44 [d:\rs1\onecore\com\combase\dcomrem\sync.cxx @ 39]
    00007ffb`79432df4 : 00000000`00000000 00000000`00000000 000000c5`eb0ff528 00000000`00000001 : combase!CoWaitForMultipleHandles+0x85 [d:\rs1\onecore\com\combase\dcomrem\sync.cxx @ 124]
    00007ffb`79434f4b : 0000022a`189bf9d0 0000022a`7c5c0e00 0000022a`7c504720 00000000`000000e4 : VSDebugEng!dispatcher::XapiWorkerThread::ExecuteSyncTask+0x90
    00007ffb`79434ee1 : 000000c5`eb0ff550 0000022a`7c5c0d30 0000022a`7c4f18e0 0000022a`7c4f24f0 : VSDebugEng!dispatcher::CXapiPhase2ObjectQueue::Flush+0x86
    00007ffb`79444613 : 0000022a`7c5c0d30 0000022a`7c48d170 00000000`80004005 00000000`0000014c : VSDebugEng!dispatcher::CXapiPhase2ObjectQueue::~CXapiPhase2ObjectQueue+0x12
    00007ffb`79433e47 : 00000000`00000000 0000022a`7c5c0d30 00000000`80004005 00000000`0000000a : VSDebugEng!dispatcher::DkmDataContainer::DispatcherClose+0x4c
    00007ffb`79431359 : 0000022a`7c5c0d30 0000022a`7c48a710 00007ffb`7968a100 0000022a`7c48a700 : VSDebugEng!dispatcher::CServerTransportFactory::Uninitialize+0x85
    00007ff7`d08d138e : 00000000`80070000 0000022a`7c49dfa0 0000022a`7c48a700 00000000`00000004 : VSDebugEng!DkmDllUninitialize+0x9
    00007ff7`d08d1991 : 000000c5`eb0f0202 00000000`00000000 0000022a`7c4820f0 00000000`00000001 : msvsmon!msvsmon::CChildServer::Listen+0x1d2
    00007ff7`d08d1812 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : msvsmon!msvsmon::CChildServer::Main+0x159
    00007ff7`d09365d6 : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!WinMain+0x228
    00007ffb`96638364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!__scrt_common_main_seh+0x11e
    00007ffb`98c65e91 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
    00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
    Friday, March 17, 2017 12:50 AM
    |