open address sanitizer flag,my app crash

中华王 1

When there are some binary modules in my process, the runtime options are / MT and / MD. When I open asan, it will crash. Why?
In addition to keeping all binaries consistent with the runtime library, what else can I do？who can help me T_T
Call Stack:
ntdll.dll!_RtlpBreakPointHeap@4 () Unknown
ntdll.dll!RtlpValidateHeapEntry() Unknown
ntdll.dll!RtlValidateHeap() Unknown
KernelBase.dll!_HeapValidate@12 () Unknown
ucrtbased.dll!_CrtIsValidHeapPointer(const void * block) Line 1407 C++
ucrtbased.dll!free_dbg_nolock(void * const block, const int block_use) Line 904 C++
ucrtbased.dll!_free_dbg(void * block, int block_use) Line 1030 C++
ucrtbased.dll!_freea_crt(void * memory) Line 317 C++
ucrtbased.dll!__crt_scoped_stack_ptr<wchar_t>::~__crt_scoped_stack_ptr<wchar_t>() Line 456 C++
ucrtbased.dll!__acrt_GetStringTypeA(__crt_locale_pointers * locale, unsigned long info_type, const char * string, int string_size_in_bytes, unsigned short * char_type, int code_page, int error) Line 99 C++
ucrtbased.dll!setSBUpLow(__crt_multibyte_data * ptmbci) Line 628 C++
ucrtbased.dll!_setmbcp_nolock(int codepage, __crt_multibyte_data * ptmbci) Line 744 C++
ucrtbased.dll!setmbcp_internal(const int requested_codepage, const bool is_for_crt_initialization, __acrt_ptd * const ptd, __crt_multibyte_data * * const current_multibyte_data) Line 424 C++
ucrtbased.dll!__acrt_initialize_multibyte() Line 919 C++

ucrtbased.dll!__acrt_execute_initializers(const __acrt_initializer * first, const __acrt_initializer * last) Line 25 C++

ucrtbased.dll!__acrt_initialize() Line 287  C++
ucrtbased.dll!DllMainProcessAttach() Line 24    C++
ucrtbased.dll!DllMainDispatch(HINSTANCE__ * __formal, const unsigned long fdwReason, void * const lpReserved) Line 63   C++
ucrtbased.dll!__acrt_DllMain(HINSTANCE__ * const hInstance, const unsigned long fdwReason, void * const lpReserved) Line 101    C++
ntdll.dll!_LdrxCallInitRoutine@16 ()    Unknown
ntdll.dll!LdrpCallInitRoutine() Unknown
ntdll.dll!LdrpInitializeNode()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpPrepareModuleForExecution()   Unknown
ntdll.dll!LdrpLoadDllInternal() Unknown
ntdll.dll!LdrpLoadDll() Unknown
ntdll.dll!LdrLoadDll()  Unknown
KernelBase.dll!LoadLibraryExW() Unknown
wemeetapp.exe!CAppModule::LoadModuleDll() Line 293  C++

Tianyu Sun-MSFT 27,106 Reputation points Microsoft Vendor

2021-12-06T09:01:14.577+00:00

Hi @中华王 , did you do something to configure the AddressSanitizer? Could you share some steps with me to reproduce this issue?
中华王 1 Reputation point

2021-12-07T12:01:00.533+00:00
I have two modules with asan enabled.
Their calling method is exe calling DLL through loadlibrary.
When the runtime library of exe is / MT. DLL runtime library is / MD.
An error will be reported after startup.
output:
==49956==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
This can happen for multiple possible reasons:

There is a module in the range of the shadow memory

Some binaries are compiled with the Static CRT /MT(d) and some are built
with the Dynamic CRT /MD(d)

this needs to be consistent across all binaries in a process, or ASan may
try to initialize the runtime twice

The function stack may be in the range of the shadow memory. This can
sometimes be worked around by restarting the computer and trying again
==49956==ASan shadow was supposed to be located in the [0x2fff0000-0x3fffffff] range.
==49956==Dumping process modules:

My running environment:
Microsoft Visual Studio Professional 2019 16.11.7
OS verison：10.0.19043.1348

I want to know after opening asan. Why can't modules with runtime libraries of / MT and / MD be mixed
中华王 1 Reputation point

2021-12-07T12:02:42.37+00:00

==49956==Dumping process modules:
0x00e30000-0x0135c000 D:\test_source\testASan\Release\testASan1.exe
0x582c0000-0x582c8000 D:\test_source\testASan\Release\testAsanDll1.dll
0x6ed20000-0x6ed8d000 C:\windows\SYSTEM32\MSVCP140.dll
0x70b50000-0x70b64000 C:\windows\SYSTEM32\VCRUNTIME140.dll
0x75660000-0x7571f000 C:\windows\System32\RPCRT4.dll
0x75720000-0x75795000 C:\windows\System32\sechost.dll
0x75f20000-0x75f9a000 C:\windows\System32\ADVAPI32.dll
0x768d0000-0x76ae4000 C:\windows\System32\KERNELBASE.dll
0x76b40000-0x76c30000 C:\windows\System32\KERNEL32.DLL
0x770c0000-0x7717f000 C:\windows\System32\msvcrt.dll
0x77210000-0x77330000 C:\windows\System32\ucrtbase.dll
0x77710000-0x778b3000 C:\windows\SYSTEM32\ntdll.dll
0x7bce0000-0x7c2ed000 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\HostX86\x86\clang_rt.asan_dynamic-i386.dll
I see the call stack. Asan crashed。
中华王 1 Reputation point

2021-12-07T12:03:00.53+00:00

call stack：
clang_rt.asan_dynamic-i386.dll!__sanitizer::internal__exit(int) 未知
clang_rt.asan_dynamic-i386.dll!__sanitizer::Die(void) 未知
clang_rt.asan_dynamic-i386.dll!__asan::InitializeShadowMemory(void) 未知
clang_rt.asan_dynamic-i386.dll!__asan::AsanInitInternal() 未知
ucrtbase.dll!__initterm () 未知
clang_rt.asan_dynamic-i386.dll!dllmain_crt_process_attach() 未知
clang_rt.asan_dynamic-i386.dll!dllmain_crt_dispatch() 未知
clang_rt.asan_dynamic-i386.dll!dllmain_dispatch() 未知
clang_rt.asan_dynamic-i386.dll!__DllMainCRTStartup@12 () 未知
ntdll.dll!_LdrxCallInitRoutine@16 () 未知
ntdll.dll!LdrpCallInitRoutine() 未知
ntdll.dll!LdrpInitializeNode() 未知
ntdll.dll!LdrpInitializeGraphRecurse() 未知
ntdll.dll!LdrpInitializeGraphRecurse() 未知
ntdll.dll!LdrpPrepareModuleForExecution() 未知
ntdll.dll!LdrpLoadDllInternal() 未知
ntdll.dll!LdrLoadDll() 未知
KernelBase.dll!LoadLibraryExW() 未知
KernelBase.dll!_LoadLibraryW@4 () 未知

testASan1.exe!main() 行 55 C++
中华王 1 Reputation point

2021-12-07T12:03:17.027+00:00

I want to know after opening asan. Why can't modules with runtime libraries of / MT and / MD be mixed
中华王 1 Reputation point

2021-12-09T03:50:53.577+00:00
This is the problem I encountered. I'd like to ask Microsoft. Why can't / MD and / mt be mixed。Is there any special reason。If mixed, asan will directly report an error:
If asan is enabled for both modules, but the runtime library options are inconsistent!
Some binaries are compiled with the Static CRT /MT(d) and some are built with the Dynamic CRT /MD(d)

this needs to be consistent across all binaries in a process, or ASan may try to initialize the runtime twice，

156008-error.png
中华王 1 Reputation point

2021-12-09T03:52:28.3+00:00

I mainly want to know why the runtime libraries of the two modules are inconsistent, and why they can't run after asan is enabled. Can you tell me what to do?
Tianyu Sun-MSFT 27,106 Reputation points Microsoft Vendor

2021-12-09T05:59:13.367+00:00

Hi @中华王 , it is described here: /MD,/MT,/LD(Use Run-Time Library).

All modules passed to a given invocation of the linker must have been compiled with the same run-time library compiler option (/MD,/MT,/LD).

/MT causes the application to use the multithread, static version of the run-time library(static) and /MD causes the application to use the multithread-specific and DLL-specific version of the run-time library(dynamic). The rule is to use one of them and keep consistent, they are mutually exclusive.
RLWA32 40,276 Reputation points

2021-12-09T10:10:50.41+00:00
Some binaries are compiled with the Static CRT /MT(d) and some are built with the Dynamic CRT /MD(d)

this needs to be consistent across all binaries in a process, or ASan may try to initialize the runtime twice

The ASAN message explained the problem. When you have modules that are built with /MT and with /MD then there are two instances of the runtime library present in the process.
中华王 1 Reputation point

2021-12-16T02:27:16.747+00:00

But my work scenario is a project where / MT and / MD coexist. Is there any good solution to this situation
中华王 1 Reputation point

2021-12-16T02:31:05.18+00:00

I understand that in normal development, there is no problem with the mixing of runtime libraries.
Because some modules just want to control heap space independently.
Prevent other modules from polluting their own memory.
This is my current development scenario.
But it won't work when asan is turned on.
Is there a solution to this situation?
RLWA32 40,276 Reputation points

2021-12-16T12:30:05.993+00:00

I understand that in normal development, there is no problem with the mixing of runtime libraries.

This may not be the case if you aren't very careful. I suggest you read Potential Errors Passing CRT Objects Across DLL Boundaries
中华王 1 Reputation point

2021-12-17T11:22:50.547+00:00

By analyzing the source code of Asan,
I found the reason why it can't be mixed. This seems to be a bug in asan.
Asan will create a shadowmemory during initialization.
Asan in / mt scenario and / MD scenario. Will call the side initialization function.
This function will call the creation function of shadowmemory.
Shadowmemory is a fixed area specified by an offset address.
When this area is created, an error will be reported when an asan is created again.
Call abort directly to exit the process. This should be caused by the mixing of different runtime libraries in a process。
asan source: https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/asan/asan_shadow_setup.cpp
RLWA32 40,276 Reputation points

2021-12-17T11:28:32.95+00:00

Maybe its a bug. Maybe its a design choice in the implementation. In any event, its an issue for the Asan developers.