On 12/17/2013 03:17 AM, Claus Assmann wrote:
Can you please try putting a breakpoint on sha1_block_data_order_ssse3,
and checking what the value of %rsp is at the start of the function?
Breakpoint 5, sha1_block_data_order_ssse3 () at sha1-x86_64.s:1295
1295pushq %rbx
Current language:
On Tue, Dec 17, 2013, Florian Weimer wrote:
Current language: auto; currently asm
(gdb) p $rsp
$15 = (void *) 0x8007360a0
Actually, it doesn'ton function entry, %rsp must be congruent 8 modulo 16.
Thanks for the clarification, I misunderstood 16-byte stack alignment.
The problem seems to
On 12/14/2013 05:50 PM, Claus Assmann wrote:
Program received signal SIGBUS, Bus error.
sha1_block_data_order_ssse3 () at sha1-x86_64.s:1328
1328movdqa %xmm0,0(%rsp)
movdqa needs 16-byte alignment.
rsp0x800736048 0x800736048
%rsp is only 8-byte aligned.
This
On 14 Dec 2013, at 17:50, Claus Assmann ca+ssl-...@esmtp.org wrote:
I'm getting a crash in sha1_block_data_order_ssse3() but currently
I don't know how to debug this further as I'm not very familiar
with the internals... Any suggestions for tracking this down are
appreciated, e.g., is it
Claus Assmann wrote:
I'm getting a crash in sha1_block_data_order_ssse3() but currently
I don't know how to debug this further as I'm not very familiar
with the internals... Any suggestions for tracking this down are
appreciated, e.g., is it something in the application or in OpenSSL?
The
Claus Assmann wrote:
I'm getting a crash in sha1_block_data_order_ssse3() but currently
I don't know how to debug this further as I'm not very familiar
with the internals... Any suggestions for tracking this down are
appreciated, e.g., is it something in the application or in OpenSSL?
The
On Sun, Dec 15, 2013, Dimitry Andric wrote:
Program received signal SIGBUS, Bus error.
sha1_block_data_order_ssse3 () at sha1-x86_64.s:1328
1328movdqa %xmm0,0(%rsp)
rsp0x800736048 0x800736048
This is most likely a stack alignment problem. The movdqa
I'm getting a crash in sha1_block_data_order_ssse3() but currently
I don't know how to debug this further as I'm not very familiar
with the internals... Any suggestions for tracking this down are
appreciated, e.g., is it something in the application or in OpenSSL?
The problem is 100% reproducible
