Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-08-07 Thread BERTRAND Joel
Andy Polyakov via RT a écrit : Could you 'truss -v sigaction,sigprocmask apps/openssl version' and submit output? I cannot. My server doesn't run Solaris but Linux/sparc. I just have seen the same bug a long time ago on Solaris but I don't have any solaris server anymore. Then run 'stra

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-08-07 Thread Andy Polyakov via RT
>>> Could you 'truss -v sigaction,sigprocmask apps/openssl version' and >>> submit output? >> I cannot. My server doesn't run Solaris but Linux/sparc. I just have >> seen the same bug a long time ago on Solaris but I don't have any >> solaris server anymore. > Then run 'str

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-08-07 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : >> Could you 'truss -v sigaction,sigprocmask apps/openssl version' and >> submit output? > I cannot. My server doesn't run Solaris but Linux/sparc. I just have > seen the same bug a long time ago on Solaris but I don't have any > solaris server a

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-08-07 Thread Andy Polyakov via RT
> Could you 'truss -v sigaction,sigprocmask apps/openssl version' and > submit output? I cannot. My server doesn't run Solaris but Linux/sparc. I just have seen the same bug a long time ago on Solaris but I don't have any solaris server anymore. >>> Then run 'strace -v app

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-22 Thread David Jacobson
On 7/18/2011 5:46 AM, Andy Polyakov via RT wrote: Hi, [snip] If I add printf() in signal handler, I see that it is called, and that siglongjmp() works. With my printf(), my program doesn't abort with SIGILL anymore but with SIGBUS (?!). It is illegal for a signal handler to call an

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-20 Thread David Jacobson via RT
On 7/18/2011 5:46 AM, Andy Polyakov via RT wrote: > Hi, > > [snip] >> >> If I add printf() in signal handler, I see that it is called, and that >> siglongjmp() works. With my printf(), my program doesn't abort with >> SIGILL anymore but with SIGBUS (?!). > It is illegal for a signal handler t

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-20 Thread Andy Polyakov via RT
> I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks > sparc capabilities with SIGILL signal. On sparc64 (both Linux and > solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called > and program terminates with SIGILL in _sparcv9_fmadd_probe: >

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-20 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with SIGILL in

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-19 Thread BERTRAND Joel
Andy Polyakov via RT a écrit : I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with SIGILL in _sparcv9_fmad

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-19 Thread BERTRAND Joel
Andy Polyakov via RT a écrit : Hi, Hello, I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with SIGILL in

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread Andy Polyakov via RT
>>> I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks >>> sparc capabilities with SIGILL signal. On sparc64 (both Linux and >>> solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called >>> and program terminates with SIGILL in _sparcv9_fmadd_probe: >>> >>>

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread BERTRAND Joel via RT
Andy Polyakov via RT a écrit : > Hi, Hello, >> I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks >> sparc capabilities with SIGILL signal. On sparc64 (both Linux and >> solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called >> and program terminate

Re: [openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-18 Thread Andy Polyakov via RT
Hi, > I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks > sparc capabilities with SIGILL signal. On sparc64 (both Linux and > solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called > and program terminates with SIGILL in _sparcv9_fmadd_probe: > > 0

[openssl.org #2553] [Bug report] SIGILL on sparc64 (linux/solaris)

2011-07-01 Thread BERTRAND Joel via RT
Hello, I see a very strange bug in crypto/sparcv9cap.c. OpenSSL 1.0.0d checks sparc capabilities with SIGILL signal. On sparc64 (both Linux and solaris, with UltraSPARC III+ and T1 CPU's), SIGILL handler is called and program terminates with SIGILL in _sparcv9_fmadd_probe: