There is no 'debug mode' of OpenSSL. However, please note that OpenSSL doesn't check its pointers to make sure that they're valid before trying to use them.
So, how is it aborting? Is it aborting due to invalid memory access? Is it aborting due to a breakpoint? Or is it just failing and your code doesn't know how to handle it so it just abort()s? Are you dealing with any kind of multiple threading? (I know embedded platforms generally don't have threads, but I have to ask.) Usually, an error like this means that some data structure that the library expects to be initialized is not, in fact, initialized properly, and is pointing to uninitialized or unallocated memory. However, you might have a different problem. If you do not have an actual stdio implementation (many embedded systems don't provide one), you shouldn't be getting any calls to that function. Do you have a backtrace of the function call stack? -Kyle H 2008/10/7 曹飞 <[EMAIL PROTECTED]>: > I am using openssl in arm embedded platform. I want to support https, so it > will use openssl. But I have encouterd some problem. The application aborted > for some unknown reason. I tried to trace the problem and found the it > aborted on call "PEM_read_bio_X509" (ssl_rsa.c). And I can't trace deep > more. > > So is there any way to enable debug mode of openssl so that I can trace more > deeply to find out the problem? > > Thanks. > Elven > > ________________________________ > MSN上小游戏，工作休闲两不误！ 马上就开始玩！
