The two additional options didn't add any info. set PATH=C:\Program Files (x86)\OpenConnect;%PATH% "openconnect.exe" -v -v --no-dtls usgaclient.vpn.att.com Faulting application name: openconnect.exe, version: 0.0.0.0, time stamp: 0x54ca5503 Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722 Exception code: 0xc0000005 Fault offset: 0x0000b080 Faulting process id: 0x580 Faulting application start time: 0x01d03be0ed3bacbf Faulting application path: C:\Program Files (x86)\OpenConnect\openconnect.exe Faulting module path: C:\Windows\syswow64\msvcrt.dll Report Id: 440b2011-a7d4-11e4-b98e-00059a3c7a00 Oh, incidentally I copied those routines into the existing folder: C:\Program Files (x86)\OpenConnect . Now openconnect-gui crashes immediately with: "The procedure entry point gnutls_system_key_iter_deinit could not be located in the dunamic link library libgnutls-28.dll . -----Original Message----- From: David Woodhouse Sent: Thursday, January 29, 2015 11:25 AM To: Steven Petraglia Cc: Niels Peen ; openconnect-devel at lists.infradead.org Subject: Re: OpenConnect v6 Core Dump On Thu, 2015-01-29 at 11:06 -0500, Steven Petraglia wrote: > One new message "signer not found", but dumped in same place. > It seems to be dying in a call to a Microsoft routine: > C:\Windows\syswow64\msvcrt.dll, version: 7.0.7601.17744 > > Do I have the correct Visual C version? Oh Windows, how we hate thee. Is there no way you can get a backtrace of *where* it actually crashed? Can you add '-v -v' to the command line? And also see if '--no-dtls' makes it go away? At least that'll give us a little more clue. -- dwmw2
