qq952670771 commented on issue #557: URL: https://github.com/apache/logging-log4cxx/issues/557#issuecomment-3470983393
> There isn't any simple code change available that always avoids SIOF. Using a separate dll for Log4cxx extension code is the only general approach. It is similar to the fix that C++ modules offers. > > However, I am now not certain your problem is SIOF. An exception when calling `delete` usually means the heap is corrupt (eg. heap buffer overflow, use after free etc). > > That would mean the problem is elsewhere in your code and the symptom you are seeing in `log4cxx::helpers::ClassRegistration::ClassRegistration` is because it is a heap operation after the heap was corrupted. > > To isolate heap corruption you need to use address sanitizer options on the compiler, or cut modules from your application until the problem dissappears. It should be the problem you mentioned - SIOF. I moved the corresponding initialization code to the simplest project and also loaded the corresponding log4cxx.dll. There were no issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
