On 10/10/14 10:15, Andy Polyakov wrote:
If I press ‘continue’, then also it give segmentation fault. It is not
working normally, it exits with seg fault: saying illegal
instruction.
??? Segmentation fault != illegal instruction. What does "exits with seg
fault saying illegal instruction" mean? Where is the segmentation fault?
Could you suggest any other solution? The assembly
instruction which I mentioned in my log was identified as illegal
instruction.
https://www.openssl.org/support/faq.html#PROG17. There are two options
listed.
As Fedor mentioned, it is expected to see some SIGILL at the beginning
of the OpenSSL application as that's how OpenSSL checks the hardware
capabilities. If you are running your application with a debugger, a
debugger may catch SIGILL signals multiple times, so you may have to hit
"continue" multiple times to resume.
As explained in the FAQ page listed by Andy, you can workaround it by:
/@ == gdb ==/
/@ adding 'handle SIGILL nostop' to your .gdbinit./
/@ == mdb ==/
/@ running '4:i' at the mdb prompt./
Once you set the workaround, the debugger ignores SIGILL so that you
don't have to hit "continue".
-- misaki
Oracle Solaris Security
Senior Software Engineer
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
