I am assuming that running the application under Valgrind at the client
site to catch the crash is not an option.
Suggestions in order of least amount of pain. Since I see .dll in your
output I will also assume Windows platform.
1.) Run CppCheck and other static source analysis tools to make
Hello!
Given the issue (heap corruption) and lack of symbols for openssl it's somewhat
hard to determine.
With heap corruption it could be a buffer overflow somewhere else in the
application which is then caught during the malloc call.
Mårten
From: Inte
