ARM is one of those awkward processors, the event counter isn't always directly readable from userspace, if it's not directly readable you get an illegal instruction trap. A syscall to access the event counters is only present in recent kernels. And even more fun, the event counter data is only r
Strange, but now on the same machine everything works fine.
Seems it was fluctuations of world ether...
On 21 September 2014 15:08, Andrey Kulikov via RT wrote:
> # uname -a
> Linux deb7 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
> # gcc --version
> gcc-4.7.real (Debian 4.7.2-5
Let's fix it the right way. :)
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me Twitter: RichSalz
:��I"Ϯ��r�m
(Z+�7�zZ)���1���x ��hW^��^��%�� ��&jם.+-1�ځ��j:+v���h�
Is there any time that the value of HOST_cl2 is used? Could we just add the
(void) cast to the macro definition?
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me Twitter: RichSalz
__
OpenSSL Project
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? W
> 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?
> C
Jay,
I seen the reports of this error on node.js issue tracker, but don't have
any other information about it yet, since I'm unable to reproduce it on my
raspberry pi.
What I tried to say, is that Illegal instruction and the SIGILL is the way
OpenSSL tries to figure out the supported features. It
Hi Fedor,
If I press ‘continue’, then also it give segmentation fault. It is not working
normally, it exits with seg fault: saying illegal instruction.Could you suggest
any other solution? The assembly instruction which I mentioned in my log was
identified as illegal instruction.
Thanks,
Jay
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
