InDllSecur.c, you use lstrcatW for concatenting strings. There's no need for this, which catches SEH exceptions too. Use wcscat or wcscat_s instead.
Aha! Now we're getting somewhere. In that file the code is: ``` #ifndef _AFX typedef CAtlStringW CStringW; ifdef _ATL_USE_WINAPI_FAMILY_DESKTOP_APP typedef CAtlStringA CStringA; endif // _ATL_USE_WINAPI_FAMILY_DESKTOP_APP typedef CAtlString CString; endif `` However, since I'm plugging this into a mostly MFC application (because I hate MFC),_AFXis defined. In the long run, this should be fixed, but in the meantime, should I just#undef _AFX` (or will that break everything else?)
ATL CString issues
Need ability to handle much longer strings
potentially uninitialized local variable in FilterBank
Debugging symbols for ffdshow?
MAYBE using uninitialized memory in hunspell:497
Using uninitialized memory in hunspell.cxx:452 (related to local variable shadowing in #273)