On Wed, Jan 16, 2002 at 04:23:03PM +0100, Daniel Stenberg wrote:

> With some additional I-modified-almost-every-single-file style hacking, I
> think I've got most of libcurl to work (at least pretty good) with the
> non-blocking sockets it now uses internally all the time.
>
> To celebrate this event, I thought I'd invite you all to torture the
> 7.9.3-pre2 sources I've stashed in the normal place:
> http://curl.haxx.se/beta/

Hm, still having situations, where curl stops with an error but gives no
error-message:

    $ src/curl -i -v --connect-timeout 1 https://meine.db24.de/
    * Closing connection #0
    curl: (28)

But in other cases it dumps core:

    $ src/curl -i -v https://meine.db24.de/
    * SSL connection using RC4-MD5
    * Server certificate:
    * subject: /C=DE/ST=Hessen/L=Frankfurt/O=Deutsche Bank AG/OU=Deutsche Bank 24 AG/OU=Terms of use at www.verisign.com/RPA (c)00/CN=meine.db24.de
    * start date: 2001-06-13 00:00:00 GMT
    * expire date: 2002-07-13 23:59:59 GMT
    * common name: meine.db24.de (matched)
    * issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign International Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign
    * Connected to meine.db24.de (193.150.167.1)
> GET / HTTP/1.1
    User-Agent: curl/7.9.3-pre2 (i686-pc-linux-gnu) libcurl 7.9.3-pre2 (OpenSSL 0.9.6)
    Host: meine.db24.de
    Pragma: no-cache
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

    Segmentation fault (core dumped)

Unfortunately, i cannot make a backtrace with gdb:

    $ gdb --core core
    GNU gdb 4.18
    [...]
    Core was generated by `lt-curl -i -v https://meine.db24.de/'.
    Program terminated with signal 11, Segmentation fault.
    #0 0x4015ab2e in ?? ()
    (gdb) where
    #0 0x4015ab2e in ?? ()
    #1 0x40069d10 in ?? ()
    #2 0x208877cb in ?? ()
    Cannot access memory at address 0xcefb67b4.
    (gdb)

Tested on my linux system with kernel 2.2.13, libc 2.1.2 and openssl
9.9.6.

Bye,
Georg
Received on 2002-01-16