>>From Dennis Clarke <[email protected]> > To [email protected] > Date Fri, 01 Mar 2013 17:21:54 -0500 > Subject openssl 1.0.1e throws SIGILL on Solaris 10 sparc64 > > I am seeing a sigILL when I attempt to debug or > single step through code. > > ... > > Would be nice to track this down as it is very consistent and stops > any attempts to use a debugger.
There is nothing to track down, as it's intentional behaviour. If SPARC would maintain capability vector, or at least expose CPU model to unprivileged code, then it wouldn't be necessary to try its capabilities by such brutal methods as testing if specific extension instructions such as fmadd crash or not. As for stopping debugging attempts. You are not prevented to debugging. Under debugger you can simply resume execution and let signal handler handle the exception. If you find it inappropriate to be required to resume execution you can set environment variable OPENSSL_sparcv9cap to say 1 prior invoking the debugger so that the probing code won't run and you won't be disturbed. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
