Hello John, Thanks. On casual inspection, that seems very sad. It has failed, and seems to be trying to tell us that nothing is wrong. My next experiment is: gdb <the usual stuff> break ERR_put_error run bt 10 quit to try to prove, upstream, that there really was a complaint. Regards, James. On 24/02/2016, John Found <johnfound at asm32.info> wrote:
On Wed, 24 Feb 2016 10:34:00 +1300 James C <james.from.wellington at gmail.com> wrote:
Hello John,
I'm a bit better off, but not necessarily a lot. Unless someone takes this off me and instantly solves it, please presume that it's a long journey.
I do not reproduce the problem. It may depend on the set of certificates on your machine, or something painful like that.
I propose to attempt to give you a cookbook for driving gdb. You could try going which dillo
Program received signal SIGABRT, Aborted. 0x00007ffff5dfe3c8 in raise () from /usr/lib/libc.so.6 (gdb) print ERR_peek_last_error() $1 = 0 (gdb) print /x ERR_peek_last_error() $2 = 0x0 (gdb) bt 10 #0 0x00007ffff5dfe3c8 in raise () from /usr/lib/libc.so.6 #1 0x00007ffff5dff84a in abort () from /usr/lib/libc.so.6 #2 0x00007ffff5df72c7 in __assert_fail_base () from /usr/lib/libc.so.6 #3 0x00007ffff5df7372 in __assert_fail () from /usr/lib/libc.so.6 #4 0x0000000000447a01 in a_Tls_handshake (fd=7, url=0xb005f0) at tls.c:1177 #5 0x0000000000444e6b in Http_connect_tls (info=0xb00470) at http.c:512 #6 Http_connect_socket (Info=0xb00470) at http.c:584 #7 Http_connect_queued_sockets (srv=0xb00800) at http.c:275 #8 0x0000000000445a6c in Http_get (Data1=0xaffa20, Info=0xb00470) at http.c:742 #9 a_Http_ccc (Op=<optimized out>, Branch=<optimized out>, Dir=<optimized out>, Info=0xb00470, Data1=0xaffa20, Data2=0x0) at http.c:833 (More stack frames follow...)
-- http://fresh.flatassembler.net http://asm32.info John Found <johnfound at asm32.info>