Parimal Das wrote:
Its the second case Darry,
Here the 'sleep' is Operating System Sleep mode induced by closing the
lid of laptop.
After opening the laptop, when the system wakes up,
My application is always hanging at the same place.
It is possible there is something specific OSX does in relation to
restarting the application.
Knowing the call function trace is a start but you need to rebuild the
application with full debugging and insert some logging. What you want
to be able to do to this mailing list is describe the sequence of event
that take place.
So you need to describe the entire situation:
* From the context of the kernel system calls the application is
making, including return codes and data. On linux strace is a command
line tool that can do this.
* Dig into the code and describe the sleep/wake mechanism used.
You then need to work out from the code base of the application which
party is taking responsibility for what matters relating to socket IO.
I.e. the application or the OpenSSL library. Its possible to delegate
most of the work to the OpenSSL library but its also possible to
override and provide custom handling inside the application.
Can you write a simple test case, this is the smallest possible program
that can reliably demonstrate the problem.
If you are not yourself a developer (software engineer) then it is
unlikely you will be able to make further progress on this matter. It
is not even clear at this time the problem is with the OpenSSL library
so the onus is on your to provide test cases to prove that. In doing
that then it maybe possible for non-OSX users to assist with the problem
and provide patches for you to test.
Darryl
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
