headers
Andrés García | 1 Dec 2004 02:04
Picon

Re: anything else before release?

Hi,

>   o Is the mingw build fine now?

No, it isn't, but the special makefiles do work, so I don't
think this is a showstoper.

Andres
Permalink | Reply | 0 comments |
headers
juergen | 1 Dec 2004 11:07

Re: https

Message-Id: <20041201100729.3336110E9B <at> schwiaa1.miniserver.com>

Czékmány Balázs <czekmany <at> microsec.hu> wrote :

> I would like to use the libcurl in my win32 program. It works fine with the 
> http request but the https just doesnt work.
> 
> The value of res is CURLE_UNSUPPORTED_PROTOCOL. I suppose it some kind of 
> openSSl problem, but i dont know what to do. The version i downoaded says
> it supports ssl.

Use the mingw library, the win32 download you took is wrongly deployed without ssl.
Permalink | Reply | 501 comments |
headers
Czékmány Balázs | 1 Dec 2004 10:55
Picon

https

Hi,

I would like to use the libcurl in my win32 program. It works fine with the 
http request but the https just doesnt work.

The value of res is CURLE_UNSUPPORTED_PROTOCOL. I suppose it some kind of 
openSSl problem, but i dont know what to do. The version i downoaded says
it supports ssl.

Tnx,

 Czékmány Balázs
Mobile: +36 30 638-76-83
Tel.: +36 1 438 6325
e-mail: czekmany <at> microsec.hu
Permalink | Reply | 0 comments |
headers
Czékmány Balázs | 1 Dec 2004 11:20
Picon

RE: https

TNX :)

-----Original Message-----
From: curl-library-bounces <at> cool.haxx.se
[mailto:curl-library-bounces <at> cool.haxx.se] On Behalf Of
juergen <at> schwietering.com
Sent: Wednesday, December 01, 2004 11:07 AM
To: libcurl development
Subject: Re: https

Message-Id: <20041201100729.3336110E9B <at> schwiaa1.miniserver.com>

Czékmány Balázs <czekmany <at> microsec.hu> wrote :

> I would like to use the libcurl in my win32 program. It works fine with
the 
> http request but the https just doesnt work.
> 
> The value of res is CURLE_UNSUPPORTED_PROTOCOL. I suppose it some kind of 
> openSSl problem, but i dont know what to do. The version i downoaded says
> it supports ssl.

Use the mingw library, the win32 download you took is wrongly deployed
without ssl.
Permalink | Reply | 501 comments |
headers
Daniel Stenberg | 1 Dec 2004 11:27
Picon
Favicon

Re: Memory problem with Windows

On Tue, 30 Nov 2004, Gonzalo Diethelm wrote:

> The symptom: the program is killed when calling curl_easy_cleanup(). When 
> run inside MSVC's debugger, I get the following stack trace:

I can't say that helped me much...

> I have ported the EXACT same code to linux and run it with efence. Alas, the 
> problem in linux is not replicated; the program finishes without any 
> problems there (same thing WITHOUT efence).

The problem is very likely to be in your code, not in libcurl.

If you believe otherwise, I urge you to create an as tiny program as possible 
that repeats the problem and post it here for us to try/debug/test.

> If I had to guess, I would think something is overwriting memory somewhere. 
> My hopes were high for linux and efence, but alas, the program works 
> flawlessly there.

valgrind is actually a better tool for linux and memory-related problems.

> Anybody has any suggestions? Are there any known memory-related bugs in 
> libcurl under Windows?

in libcurl 7.12.2: none.

--

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html
(Continue reading)

Permalink | Reply | 3 comments |
headers
Daniel Stenberg | 1 Dec 2004 11:49
Picon
Favicon

Re: anything else before release?

On Tue, 30 Nov 2004, David Phillips wrote:

> We need a safe API to get file descriptors for the multi interface.

Yes we do. You have any suggestion?

Here's my first attempt:

struct curl_filedesc {
   int num;   /* number of entries in the array below */
   int fd[1]; /* array with file descriptors */
};

CURLMcode curl_multi_fdget(CURLM *multi_handle,
 			   struct curl_filedesc *readfd,
 			   struct curl_filedesc *writefd,
 			   struct curl_filedesc *excfd);

There's one problem with using 'int' for this, as socket file descriptors 
aren't ints everywhere - which is why we use curl_socket_t internally in 
libcurl.

--

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html
Permalink | Reply | 0 comments |
headers
Gokul Soundararajan | 1 Dec 2004 18:43
Picon

C libcurl max multi connections limit

Hi,

I have designed a http client emulator using C libcurl. In the code, I 
am using the multi-interface. It seems that there is a limit of the 
number of concurrent connections when using the multi-interface.

For example, I get CURL error 7 (COULDNT_CONNECT) whenver I use more 
than 1024 concurrent connections.

If there is a limit, is there a way to increase it?

Thanks,

Gokul
Permalink | Reply | 3 comments |
headers
Gonzalo Diethelm | 1 Dec 2004 19:04

RE: Memory problem with Windows

> > The symptom: the program is killed when calling 
> curl_easy_cleanup(). 
> > When
> > run inside MSVC's debugger, I get the following stack trace:
> 
> I can't say that helped me much...

Hey, thanks for looking anyway. I have compiled libcurl with debugging
information; here is the (relevant) stack trace:

ConnectionKillOne(SessionHandle * 0x00ab4250) line 1677 + 24 bytes
Curl_close(SessionHandle * 0x00ab4250) line 206 + 9 bytes
curl_easy_cleanup(void * 0x00ab4250) line 394 + 9 bytes

Inside ConnectionKillOne() it dies when executing this line of code:

  for(i=0; i< data->state.numconnects; i++) {

The data variable is corrupted, it doesn't show any good values at all.

> valgrind is actually a better tool for linux and 
> memory-related problems.

I did try valgrind, it only shows one problem that I saw was reported in the
mailing list here:

http://marc.theaimsgroup.com/?l=sqlite-users&m=108818352518443&w=2

That, it seems to me, is not a real memory problem; it seems the call to
write() is always writing 1024 bytes (the page size), but the piece of
(Continue reading)

Permalink | Reply | 2 comments |
headers
Guillaume Arluison | 1 Dec 2004 19:08

Re: C libcurl max multi connections limit

I'll let someone else answer for libcurl itself cos I dont know the answer
(and I'm interested) but 1024 concurrent connections seems really high (and
my job is 50% of time doing stress tests and I'm already scared by a lot
less concurrent connections :))
You said that your application is a client (with curl its usual :)) so it
means your target is a server. Are you sure the server isnt already limited
by this value of 1024 connections at a time ? It's rare that you can handle
more than that in the application layer even before hitting the limit of the
kernel/network no ?
____________________
<Gu>[W]ill[i]a<u>m<e>
http://www.lacde.net
----- Original Message ----- 
From: "Gokul Soundararajan" <gokul <at> eecg.toronto.edu>
To: <curl-library <at> cool.haxx.se>
Sent: Wednesday, December 01, 2004 5:43 PM
Subject: C libcurl max multi connections limit

> Hi,
>
> I have designed a http client emulator using C libcurl. In the code, I
> am using the multi-interface. It seems that there is a limit of the
> number of concurrent connections when using the multi-interface.
>
> For example, I get CURL error 7 (COULDNT_CONNECT) whenver I use more
> than 1024 concurrent connections.
>
> If there is a limit, is there a way to increase it?
>
> Thanks,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dan Fandrich | 1 Dec 2004 19:57
Favicon

Re: C libcurl max multi connections limit

On Wed, Dec 01, 2004 at 06:08:34PM -0000, Guillaume Arluison wrote:
> I'll let someone else answer for libcurl itself cos I dont know the answer
> (and I'm interested) but 1024 concurrent connections seems really high (and
> my job is 50% of time doing stress tests and I'm already scared by a lot
> less concurrent connections :))
> You said that your application is a client (with curl its usual :)) so it
> means your target is a server. Are you sure the server isnt already limited
> by this value of 1024 connections at a time ? It's rare that you can handle
> more than that in the application layer even before hitting the limit of the
> kernel/network no ?

I would guess it's an OS or per-process limit on open sockets.  Run the
bash command ulimit -a to see what your process limits are.

>>> Dan
--

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved
Permalink | Reply | 0 comments |

Gmane