cURL / Mailing Lists / curl-library / Single Mail

curl-library

WIN7 Access Violation ~curl_easy_perform(curl)

From: Roger Cabo - gfa_at_trainzland.com <gfa_at_trainzland.com>
Date: Tue, 16 Jul 2013 01:46:39 +0200

(Windows 7)
today I tried to implement the first example of:
http://curl.haxx.se/libcurl/c/getinmemory.html

But unfortunately I got an Access Violation that comes from the libcurl.dll

Version info returned:
libcurl/7.31.0 OpenSSL/1.0.0k zlib/1.2.8 libidn/1.18 libssh2/1.4.3
librtmp/2.3

AccessViolation in:
     ~curl_easy_setopt(curl_handle, CURLOPT_URL, V:Url)
     ~curl_easy_setopt(curl_handle, CURLOPT_WRITEFUNCTION,
ProcAddr(curl_myWrite))
     ~curl_easy_setopt(curl_handle, CURLOPT_WRITEDATA, *mem)
     ~curl_easy_setopt(curl_handle, CURLOPT_VERBOSE, 1L)
     ~curl_easy_setopt(curl_handle, CURLOPT_STDERR, hNewFile)

--> ~curl_easy_perform(curl_handle)

libcurl connects to the ftp and receive the first chunk successfully.
The function curl_myWrite{} was called successfully too.

It returned the correct *content from the ftpfile
'ftp://ftp.hp.com/ftp1/pub/visualize/55RMDBTest/TopToolsRMDB.txt'
*contents = "2 FULL
ftp://ftp.hp.com/pub/visualize/55RMDBTest/TOPTOOLSRMDB.EXE"
size = 1
nmemb = 65

curl_myWrite{} returns the correct value realsize=65
Then Access Violation occur

--> ~curl_easy_perform(curl_handle)

The debug hNewFile stays 0 bytes. (Perhaps its the app<->dll fopen()
problem.)

1) - Is there another chance to receive a debug out from libcurl?
2) - Exist debugging option that writes a file by iself?

Any ideas about?

Roger

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-07-16