Mex-file error

15 次查看（过去 30 天）
sunghoon shin
sunghoon shin 2018-11-26
评论： James Tursa 2018-11-26
-------------------------------------------------------------------------------
Access violation detected at 월 11 26 06:02:42 2018 +0900
--------------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : KSC_5601
Deployed : false
Graphics Driver : NVIDIA Corporation GeForce GTX 960/PCIe/SSE2 Version 4.6.0 NVIDIA 388.13
Graphics card 1 : NVIDIA ( 0x10de ) NVIDIA GeForce GTX 960 Version 23.21.13.8813 (2017-10-27)
Java Version : Java 1.8.0_152-b16 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 2633888
MATLAB Root : C:\Program Files\MATLAB\R2018b
MATLAB Version : 9.5.0.944444 (R2018b)
OpenGL : hardware
Operating System : Microsoft Windows 10 Pro
Process ID : 235552
Processor ID : x86 Family 6 Model 63 Stepping 2, GenuineIntel
Session Key : eff9406a-39d0-4069-8272-bb677bd7a293
Window System : Version 10.0 (Build 17134)
Fault Count: 1
Abnormal termination
Register State (from fault):
RAX = 0000000000000000 RBX = 0000000000000bb8
RCX = 000000006a4e3660 RDX = 0000000000000000
RSP = 00000000043f95b0 RBP = 00000000043f9760
RSI = 0000000000000bb8 RDI = 00000000043fa4d0
R8 = 0000000000000880 R9 = 00000000043fa4d0
R10 = 0000000000000026 R11 = 00000000043f9698
R12 = 0000000000000001 R13 = 000000016735c600
R14 = 00000000043f9760 R15 = 00000000043f9760
RIP = 00000000106115d3 EFL = 00010206
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00000000106115d3 C:\VTC_F\close_ret.mexw64+00005587 mexFunction+00000259
[ 1] 0x00000000fc635524 bin\win64\libmex.dll+00349476 MexRetrieveVersion+00003348
[ 2] 0x00000000fc63571c bin\win64\libmex.dll+00349980 MexRetrieveVersion+00003852
[ 3] 0x00000000fc635884 bin\win64\libmex.dll+00350340 MexRetrieveVersion+00004212
[ 4] 0x00000000fc619059 bin\win64\libmex.dll+00233561 mexUnlock_800+00025273
[ 5] 0x000000001762e007 bin\win64\pgo\m_dispatcher.dll+00057351 Mfh_file::dispatch_fh_impl+00001111
[ 6] 0x000000001762da9e bin\win64\pgo\m_dispatcher.dll+00055966 Mfh_file::dispatch_fh+00000062
[ 7] 0x00000000184568f2 bin\win64\pgo\m_lxe.dll+00420082
[ 8] 0x000000001844ab16 bin\win64\pgo\m_lxe.dll+00371478
[ 9] 0x0000000018448e1c bin\win64\pgo\m_lxe.dll+00364060
[ 10] 0x000000001845b265 bin\win64\pgo\m_lxe.dll+00438885
[ 11] 0x000000001845a88c bin\win64\pgo\m_lxe.dll+00436364
[ 12] 0x0000000018458779 bin\win64\pgo\m_lxe.dll+00427897
[ 13] 0x00000000184590eb bin\win64\pgo\m_lxe.dll+00430315
[ 14] 0x0000000018458a49 bin\win64\pgo\m_lxe.dll+00428617
[ 15] 0x000000001762e007 bin\win64\pgo\m_dispatcher.dll+00057351 Mfh_file::dispatch_fh_impl+00001111
[ 16] 0x000000001762da9e bin\win64\pgo\m_dispatcher.dll+00055966 Mfh_file::dispatch_fh+00000062
[ 17] 0x0000000018444ead bin\win64\pgo\m_lxe.dll+00347821
[ 18] 0x00000000185de9b6 bin\win64\pgo\m_lxe.dll+02025910 MathWorks::lxe::ShutdownLxeEngine+00004034
[ 19] 0x000000001853fd3c bin\win64\pgo\m_lxe.dll+01375548 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00493568
[ 20] 0x000000001854091c bin\win64\pgo\m_lxe.dll+01378588 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00496608
[ 21] 0x0000000018541c92 bin\win64\pgo\m_lxe.dll+01383570 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00501590
[ 22] 0x00000000185428f8 bin\win64\pgo\m_lxe.dll+01386744 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00504764
[ 23] 0x0000000018541ddf bin\win64\pgo\m_lxe.dll+01383903 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00501923
[ 24] 0x0000000018541ede bin\win64\pgo\m_lxe.dll+01384158 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00502178
[ 25] 0x0000000018449a7d bin\win64\pgo\m_lxe.dll+00367229
[ 26] 0x000000001845b265 bin\win64\pgo\m_lxe.dll+00438885
[ 27] 0x000000001845a88c bin\win64\pgo\m_lxe.dll+00436364
[ 28] 0x00000000184542a1 bin\win64\pgo\m_lxe.dll+00410273
[ 29] 0x00000000184539c6 bin\win64\pgo\m_lxe.dll+00408006
[ 30] 0x0000000018453ace bin\win64\pgo\m_lxe.dll+00408270
[ 31] 0x0000000018633780 bin\win64\pgo\m_lxe.dll+02373504 mwboost::archive::detail::oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::CodeClearEvent>::oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::CodeClearEvent>+00012824
[ 32] 0x000000001863372e bin\win64\pgo\m_lxe.dll+02373422 mwboost::archive::detail::oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::CodeClearEvent>::oserializer<mwboost::archive::xml_oarchive,MathWorks::lxe::CodeClearEvent>+00012742
[ 33] 0x00000000185134fd bin\win64\pgo\m_lxe.dll+01193213 mwboost::archive::detail::iserializer<mwboost::archive::binaryTerm_iarchive,MathWorks::lxe::function_descriptor>::load_object_data+00311233
[ 34] 0x00000000178869e7 bin\win64\pgo\m_interpreter.dll+00354791 inEvalCmdWithLocalReturn+00000063
[ 35] 0x00000000fb610388 bin\win64\libmwbridge.dll+00131976 mnParser+00001304
[ 36] 0x0000000017423618 bin\win64\mcr.dll+00341528 mcr::runtime::setInterpreterThreadSingletonToCurrent+00020808
[ 37] 0x000000001742414d bin\win64\mcr.dll+00344397 mcr::runtime::setInterpreterThreadSingletonToCurrent+00023677
[ 38] 0x00000000173eb1ba bin\win64\mcr.dll+00111034 mcrOptions::set_use_license_manager+00075498
[ 39] 0x0000000017406e74 bin\win64\mcr.dll+00224884 mcrOptions::set_use_license_manager+00189348
[ 40] 0x00000000fd02cfee bin\win64\iqm.dll+00643054 iqm::PackagedTaskPlugin::execute+00000894
[ 41] 0x00000000fd02ce63 bin\win64\iqm.dll+00642659 iqm::PackagedTaskPlugin::execute+00000499
[ 42] 0x00000000fcffcc07 bin\win64\iqm.dll+00445447 iqm::Iqm::setupIqmFcnPtrs+00076215
[ 43] 0x00000000fcffcc59 bin\win64\iqm.dll+00445529 iqm::Iqm::setupIqmFcnPtrs+00076297
[ 44] 0x00000000fcffca16 bin\win64\iqm.dll+00444950 iqm::Iqm::setupIqmFcnPtrs+00075718
[ 45] 0x00000000fcfd9748 bin\win64\iqm.dll+00300872 iqm::Iqm::deliver+00005880
[ 46] 0x00000000fcfd8eef bin\win64\iqm.dll+00298735 iqm::Iqm::deliver+00003743
[ 47] 0x00000000fcfdac0d bin\win64\iqm.dll+00306189 iqm::Iqm::deliver+00011197
[ 48] 0x0000000100203775 bin\win64\libmwservices.dll+02176885 services::system_events::PpeDispatchHook::dispatchOne+00036213
[ 49] 0x0000000100212a63 bin\win64\libmwservices.dll+02239075 sysq::addProcessPendingEventsUnitTestHook+00006035
[ 50] 0x0000000100214310 bin\win64\libmwservices.dll+02245392 sysq::getCondition+00004208
[ 51] 0x000000010021596d bin\win64\libmwservices.dll+02251117 svWS_ProcessPendingEvents+00000221
[ 52] 0x0000000017427724 bin\win64\mcr.dll+00358180 mcr::runtime::setInterpreterThreadSingletonToCurrent+00037460
[ 53] 0x0000000017427f16 bin\win64\mcr.dll+00360214 mcr::runtime::setInterpreterThreadSingletonToCurrent+00039494
[ 54] 0x000000001741cabf bin\win64\mcr.dll+00314047 mcr_process_events+00001007
[ 55] 0x000000001732d040 bin\win64\MVMLocal.dll+00380992 mvm_server::inproc::LocalFactory::terminate+00177312
[ 56] 0x00000000fa9d9480 bin\win64\mvm.dll+01741952 mvm::detail::SessionImpl::initWithOptions+00000592
[ 57] 0x00000000fa9da170 bin\win64\mvm.dll+01745264 mvm::detail::SessionImpl::runMain+00000128
[ 58] 0x00000000fa9da395 bin\win64\mvm.dll+01745813 mvm::detail::SessionImpl::runMatlabDesktop+00000261
[ 59] 0x0000000140007036 bin\win64\MATLAB.exe+00028726 mwboost::serialization::singleton_module::unlock+00000966
[ 60] 0x0000000140007f13 bin\win64\MATLAB.exe+00032531 mwboost::serialization::singleton_module::unlock+00004771
[ 61] 0x00007ffa11f23034 C:\WINDOWS\System32\KERNEL32.DLL+00077876 BaseThreadInitThunk+00000020
[ 62] 0x00007ffa14731471 C:\WINDOWS\SYSTEM32\ntdll.dll+00463985 RtlUserThreadStart+00000033
This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.
  2 个评论
Walter Roberson
Walter Roberson 2018-11-26
we do not know which mex file was running or what was passed to it. We probably do not have access to the source code of the mex either .
James Tursa
James Tursa 2018-11-26
We would need to see the source code of the mex routine in order to help you.

请先登录，再进行评论。

请先登录，再回答此问题。

回答（0 个）

类别

在 Help Center 和 File Exchange 中查找有关 Startup and Shutdown 的更多信息

标签

产品

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by