Windows 10 run-time issue

Andy Kennedy andy.kennedy.1814 at gmail.com
Wed Oct 2 23:50:26 UTC 2019


All,



Previous versions used:



Windows 7

openssl-1.0.2s

libssh-0.9.0

VS2017

Strawberry Perl



This configuration worked without issue.  Then, MS EOL'ed Windows 7.



My configuration is now:



Windows 10

openssl-1.1.1d (someone on libssh told me that I needed this version)

VS2017

Strawberry Perl

NASM

Build instructions for x64 command console:

          set PATH=%PATH%;%USERPROFILE%\strawberry\perl\bin

          set PATH=%PATH%;%USERPROFILE%\nasm-2.14.03rc2

          cd %USERPROFILE%\source\oss\openssl-1.1.1d

          perl Configure VC-WIN64A --prefix=%USERPROFILE%\oss
--openssldir=%USERPROFILE%\oss

          nmake

          nmake test

          nmake install



Now, with Windows 10, I get a "Microsoft Visual C++ Runtime Library" box
with

the following text:

Debug Assertion Failed!



Program <mysshApp.exe>

File minkernel\crts\ucrt\src\appcrt\heap\debug_heap.cpp

Line: 908



Expression: is_block_type_valid(header->_block_use)

<snip>



So, I connect to the app with the VS debugger and find:

file: pki_crypto.c:

function:  pki_signature_from_ecdsa_blob()

line: (1769) SAFE_FREE(raw_sig_data);

is what VS claims generated this error.



>From the above description, can anyone tell me what I have done wrong in

the build?  Or, have I stumbled upon a bug?



Thanks in advance for any assistance you can provide.

Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20191002/d7e247a7/attachment.html>


More information about the openssl-users mailing list