On Thu, 10 Jun 2004, Brian Ford wrote:
> I put a call to try_to_debug in find_winsock_errno when it returned the
> default EPERM. Then, by setting
> CYGWIN="error_start=c:\cygwin\bin\gdb.exe" I can get a gdb pop up and do a
> back trace. The error was:
>
> 10093
> Either the application has not
On Fri, 21 May 2004, Christopher Faylor wrote:
> On Fri, May 21, 2004 at 05:21:19PM -0500, Brian Ford wrote:
> >On Thu, 15 Apr 2004, Christopher Faylor wrote:
> >>Corinna showed me that this was a problem in my autoload code rather
> >>than a problem with winsock. That's comforting. I guess I've
On Fri, May 21, 2004 at 05:21:19PM -0500, Brian Ford wrote:
>On Thu, 15 Apr 2004, Christopher Faylor wrote:
>>Corinna showed me that this was a problem in my autoload code rather
>>than a problem with winsock. That's comforting. I guess I've grown
>>too quick to judge Windows.
>>
>>I've checked i
I assume this email is hopeless, but I'm desperately searching for a
lead...
On Thu, 15 Apr 2004, Christopher Faylor wrote:
> Corinna showed me that this was a problem in my autoload code rather than
> a problem with winsock. That's comforting. I guess I've grown too quick
> to judge Windows.
>
On Thu, Apr 15, 2004 at 12:14:55AM -0400, Christopher Faylor wrote:
>On Thu, Apr 15, 2004 at 11:16:03AM +0800, Enzo Michelangeli wrote:
>>What I can do for the time being is to provide the testcase that Corinna
>>asked for (attached below). Here are the results:
>
>I can duplicate the behavior note
On Thu, Apr 15, 2004 at 11:16:03AM +0800, Enzo Michelangeli wrote:
>What I can do for the time being is to provide the testcase that Corinna
>asked for (attached below). Here are the results:
I can duplicate the behavior noted here.
I sent Corinna a patch in private email. I'm not thrilled with
I wrote:
- Original Message -
From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: ""Brian Ford"" <[EMAIL PROTECTED]>
Sent: Thursday, April 15, 2004 11:16 AM
Subject: Re: 1.5.9-1: socket() appears NOT to be thread-sa
- Original Message -
From: "Brian Ford" <[EMAIL PROTECTED]>
To: "Enzo Michelangeli" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, April 15, 2004 1:05 AM
Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe
> On Wed, 14 Apr 2
On Wed, 14 Apr 2004, Enzo Michelangeli wrote:
> While porting to Cygwin the Linux application "sipd"
> (http://www.sxdesign.com/index.php?page=developer&submnu=sipd ), which
> uses pthreads, I noticed that socket() calls issued concurrently by
> several threads often failed, with strerror(errno) s
On Apr 14 18:42, Enzo Michelangeli wrote:
> While porting to Cygwin the Linux application "sipd"
> (http://www.sxdesign.com/index.php?page=developer&submnu=sipd ), which
> uses pthreads, I noticed that socket() calls issued concurrently by
> several threads often failed, with strerror(errno) saying
While porting to Cygwin the Linux application "sipd"
(http://www.sxdesign.com/index.php?page=developer&submnu=sipd ), which
uses pthreads, I noticed that socket() calls issued concurrently by
several threads often failed, with strerror(errno) saying "operation not
permitted". Once I protected all t
11 matches
Mail list logo
