43
« Last post by Rich Hornay on August 19, 2012, 04:16:24 PM »
I’m seeing an Access Violation on unload in crtdll.c on line 531 using 1.7.3 or 1.7.4 (v90 or v100 toolsets) in a dynamically loaded/unloaded Windows DLL.
First-chance exception at 0x000007fefb8bc413 (jtindll.dll) in JTTest.exe: 0xC0000005: Access violation writing location 0x0000000000000410.
From crtdll.c line 531 debugging:
_pRawDllMain = 0x000007fefb8be8d0 `anonymous namespace'::run_tls_callback(void * ptr64,unsigned long,void * ptr64)
The exception appears to be handled, but I am concerned and generally don’t care for anomalous behaviors. I can provide the test if you wish, but it is pretty simple. The dll exports start() and stop(). start() creates a thread and stop() joins it. The exe just loads the dll, calls start then stop and unloads the dll. This is just native code, no managed nonsense.
Can you confirm/explain this?