[armedbear] #464: drakma / cl+ssl failure

[armedbear]

#464: drakma / cl+ssl failure
----------------------------+---------------------------------
      Reporter:  charmon    |      Owner:  Evenson Not Org
          Type:  defect     |     Status:  assigned
      Priority:  blocker    |  Milestone:  1.6.0
     Component:  libraries  |    Version:  1.6.0-dev
    Resolution:             |   Keywords:  cl+ssl, ssl, drakma
Parent Tickets:             |
----------------------------+---------------------------------

Comment (by Evenson Not Org):

 Replying to [comment:18 Evenson Not Org]:
 > Replying to [comment:16 Evenson Not Org]:
 > > > I fixed the ABCL varargs thing while I was at it
 > >
 > >
 <https://github.com/slyrus/cffi/commit/1cfc67dd367fc669875ce55d46c29e7d16b0c7c3>
 >
 > Any reason we don't get a pull request in for CFFI for this?

 With this patch, {{{1.6.0-dev}}} compiled carefully with {{{OpenJDK_64
 -Bit_Server_VM-AdoptOpenJDK-1.8.0_232-b09}}} on
 {{{x86_64-Mac_OS_X-10.14.6}}} doesn't seem to SEGV, although the
 {{{CL+SSL.TEST}}} invocation has some disturbing complaints on
 uninitialized memory in the Block IO (BIO) routines.

 {{{
 CL-USER> (fiveam:run-all-tests)

 Running test suite CL+SSL
  Running test suite CL+SSL.BADSSL-COM
   Running test WRONG.HOST ..Xf
   Running test UNTRUSTED-ROOT .
   Running test EXPIRED ..Xf
   Running test SELF-SIGNED .
  Running test COMPAT-OPENSSL-VERSION .
  Running test suite CL+SSL.VERIFY-HOSTNAME
   Running test VERIY-HOSTNAME-SUCCESS ..............
   Running test VERIFY-GOOGLE-CERT-WITHOUT-DNS .
   Running test VERIFY-GOOGLE-CERT-TELETEX-STRING .
   Running test VERIFY-GOOGLE-CERT-PRINTABLE-STRING .
   Running test VERIFY-GOOGLE-CERT-BMP-STRING .
   Running test VERIFY-GOOGLE-CERT-DNS-WILDCARD .
   Running test VERIFY-GOOGLE-CERT .
   Running test VERIFY-GOOGLE-CERT-UNIVERSAL-STRING .
   Running test VERIFY-HOSTNAME-FAIL .........
  Running test SANITY-CHECK.1 .
  Running test SANITY-CHECK.2 .
  Running test suite CL+SSL.SNI Did 41 checks.
     Pass: 39 (95%)
     Skip: 0 ( 0%)
     Fail: 2 ( 4%)

  Failure Details:
  --------------------------------
  EXPIRED []:
       Unexpected Error: #<CL+SSL::SSL-ERROR-SSL {AF89B4E}>
 A failure in the SSL library occurred on handle #<com.sun.jna.Pointer
 native at 0x7fae7eeae400 {63DDE5C2}> (return code: 1).
 SSL error queue:
 error:20080078:BIO routines:bio_write_intern:uninitialized
 ..
  --------------------------------
  --------------------------------
  WRONG.HOST []:
       Unexpected Error: #<CL+SSL::SSL-ERROR-SSL {255828B}>
 A failure in the SSL library occurred on handle #<com.sun.jna.Pointer
 native at 0x7fae7b045400 {1E7233FF}> (return code: 1).
 SSL error queue:
 error:20080078:BIO routines:bio_write_intern:uninitialized
 ..
  --------------------------------
 }}}

 The SEGV seems to be definitely happening around use openjdk11 to compile
 or run the code.

--
Ticket URL: <http://abcl.org/trac/ticket/464#comment:19>
armedbear <http://abcl.org>
armedbear