>>> What OS/platform is this, and what version of OpenSSL? >> >> Also, run 'disass ssl3_get_message' at debugger prompt, advance to >> vicinity of address provided in back-trace, 0x00007fe5a839334f in >> provided example, and send that page. I mean it's lesser point to send >> whole disass output, limit it to ~20 lines. > > 0x00007fe5a839331d <+1069>: callq *%r10 > 0x00007fe5a8393320 <+1072>: jmpq 0x7fe5a8392f4c <ssl3_get_message+92> > 0x00007fe5a8393325 <+1077>: movslq 0x60(%rbx),%r8 > 0x00007fe5a8393329 <+1081>: mov 0xa0(%rbx),%rdx > 0x00007fe5a8393330 <+1088>: mov %rbx,%r9 > 0x00007fe5a8393333 <+1091>: mov 0x50(%rbx),%rbp > 0x00007fe5a8393337 <+1095>: mov (%rbx),%esi > 0x00007fe5a8393339 <+1097>: xor %edi,%edi > 0x00007fe5a839333b <+1099>: mov 0x8(%rbp),%rcx > 0x00007fe5a839333f <+1103>: add $0x4,%r8 > 0x00007fe5a8393343 <+1107>: mov %rdx,(%rsp) > 0x00007fe5a8393347 <+1111>: mov $0x16,%edx > 0x00007fe5a839334c <+1116>: callq *%r10 > 0x00007fe5a839334f <+1119>: jmpq 0x7fe5a83930e4 > <ssl3_get_message+500>
The challenge here is to map this to source code. I was hoping that call would be direct, i.e. not *%r10, which would make the task easier. Could you 'disass 0x7fe5a83930e4' and see if there are direct calls nearby that location. You see a direct call below. Another option is to make your libssl.so binary for download somewhere. It's probably better. Could you? [Feel free to post link to me personally]. > 0x00007fe5a8393370 <+1152>: callq 0x7fe5a8372938 <ERR_put_error@plt> ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
