Hello! I'm not a OpenSSL core developer, but anyway here are some thoughts from me.
SIGILL is totally a normal condition, as it is caught by: https://github.com/openssl/openssl/blob/dabfbea7d91619b286e5d32ffc68ec7e5bd7e9bf/crypto/armcap.c#L96-L101 This is a part of detecting features, so if you wish to get more details - please enter `continue` after catching SIGILL in gdb. Thanks, Fedor. On Fri, Oct 10, 2014 at 7:52 AM, Jay D Bhatt <[email protected]> wrote: > Hi , > > > > I was working on a armv7l architecture platform and was trying to run > webruntime related library, but it was crashing _armv7_tick(). So, I did > GDB on the wrt binary and below are the logs: > > > > root:/usr/bin> gdb wrt_launchpad_daemon > > GNU gdb (GDB) 7.5.1 > > Copyright (C) 2012 Free Software Foundation, Inc. > > License GPLv3+: GNU GPL version 3 or later < > http://gnu.org/licenses/gpl.html> > > This is free software: you are free to change and redistribute it. > > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > > and "show warranty" for details. > > This GDB was configured as "armv7l-tizen-linux-gnueabi". > > For bug reporting instructions, please see: > > <http://www.gnu.org/software/gdb/bugs/>... > > Reading symbols from /usr/bin/wrt_launchpad_daemon...(no debugging symbols > found)...done. > > (gdb) run > > Starting program: /usr/bin/wrt_launchpad_daemon > > warning: File "/usr/lib/libthread_db.so.1" auto-loading has been declined > by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". > > To enable execution of this file add > > add-auto-load-safe-path /usr/lib/libthread_db.so.1 > > line to your configuration file "/root/.gdbinit". > > To completely disable this security protection add > > set auto-load safe-path / > > line to your configuration file "/root/.gdbinit". > > For more information about this security protection see the > > "Auto-loading safe path" section in the GDB manual. E.g., run from the > shell: > > info "(gdb)Auto-loading safe path" > > warning: Unable to find libthread_db matching inferior's thread library, > thread debugging will not be available. > > > > Program received signal SIGILL, Illegal instruction. > > 0x2ea486e8 in _armv7_tick () from /usr/lib/libcrypto.so.1.0.0 > > (gdb) bt > > #0 0x2ea486e8 in _armv7_tick () from /usr/lib/libcrypto.so.1.0.0 > > #1 0x2ea460ac in OPENSSL_cpuid_setup () from /usr/lib/libcrypto.so.1.0.0 > > #2 0x2aab5e0e in call_init () from /lib/ld-linux.so.3 > > #3 0x2aab5ea0 in _dl_init_internal () from /lib/ld-linux.so.3 > > #4 0x2aab8c26 in dl_open_worker () from /lib/ld-linux.so.3 > > #5 0x2aab5d2a in _dl_catch_error () from /lib/ld-linux.so.3 > > #6 0x2aab8642 in _dl_open () from /lib/ld-linux.so.3 > > #7 0x2c1dab00 in dlopen_doit () from /usr/lib/libdl.so.2 > > #8 0x2aab5d2a in _dl_catch_error () from /lib/ld-linux.so.3 > > #9 0x2c1daf54 in _dlerror_run () from /usr/lib/libdl.so.2 > > #10 0x2c1dab8a in dlopen@@GLIBC_2.4 () from /usr/lib/libdl.so.2 > > #11 0x0000a744 in main () > > (gdb) disas _armv7_tick > > Dump of assembler code for function _armv7_tick: > > => 0x2e2b76e8 <+0>: mrc 15, 0, r0, cr9, cr13, {0} > > 0x2e2b76ec <+4>: bx lr > > End of assembler dump. > > > > > > > > It seems that either the architecture platform is not able to identify the > instructions or some other reason, due to which it fails. > > Has anyone faced similar problem? Could anybody suggest some solution or > patch which can solve this issue? > > > > Thanks, > > Jay > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Information contained and transmitted by this e-mail is confidential and > proprietary to IGATE and its affiliates and is intended for use only by the > recipient. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution, copying or use of this e-mail is > strictly prohibited and you are requested to delete this e-mail immediately > and notify the originator or [email protected]. IGATE does not enter > into any agreement with any party by e-mail. Any views expressed by an > individual do not necessarily reflect the view of IGATE. IGATE is not > responsible for the consequences of any actions taken on the basis of > information provided, through this email. The contents of an attachment to > this e-mail may contain software viruses, which could damage your own > computer system. While IGATE has taken every reasonable precaution to > minimise this risk, we cannot accept liability for any damage which you > sustain as a result of software viruses. You should carry out your own > virus checks before opening an attachment. To know more about IGATE please > visit www.igate.com. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >
