On Sat, Jun 02, 2012 at 12:07:50AM +0200, Otto Meta wrote:
>
> Are you using signals or functions that use signals internally? Signals are
> a bit wonky in 1.7.9 and they seem to be pretty much broken in 1.7.12 and
> newer (I didn’t try any snapshots). Have a look at the problem I reported:
> http
On Fri, Jun 01, 2012 at 03:50:19PM -0600, Warren Young wrote:
> >
> >The basic issue is that sem_wait() is being kicked out with EINTR
> >extremely frequently (9 out of 10 times or more),
>
> Does the attached program vaguely resemble what your program is
> trying to do? It does get EINTR, but on
> The basic issue is that sem_wait() is being kicked out with EINTR
> extremely frequently (9 out of 10 times or more), which slows my code
> to a crawl as it repeatedly retries sem_wait() until it finally
> returns zero. In 1.7.9, it does not appear that sem_wait() is
> preempted in this fashion;
On 6/1/2012 1:51 PM, Ryan C. Underwood wrote:
On Fri, Jun 01, 2012 at 08:59:06PM +0200, Corinna Vinschen wrote:
If you can press a long story into a short testcase in plain C with the
bare minimum of code to reproduce the behaviour, it would be much
appreciated.
The basic issue is that sem_wa
On Fri, Jun 01, 2012 at 08:59:06PM +0200, Corinna Vinschen wrote:
> >
> > Thanks, I have no idea why I did not receive that mail. I looked for
> > "nightly builds" but that would have been why I didn't find such.
-20111216, the oldest snapshot, already produces the problem, so I
guess that at le
On Jun 1 13:40, Ryan C. Underwood wrote:
> On Fri, Jun 01, 2012 at 08:18:52PM +0200, Corinna Vinschen wrote:
> >
> > http://cygwin.com/ml/cygwin/2012-06/msg8.html
>
> Thanks, I have no idea why I did not receive that mail. I looked for
> "nightly builds" but that would have been why I didn'
On Fri, Jun 01, 2012 at 08:18:52PM +0200, Corinna Vinschen wrote:
>
> http://cygwin.com/ml/cygwin/2012-06/msg8.html
Thanks, I have no idea why I did not receive that mail. I looked for
"nightly builds" but that would have been why I didn't find such.
> And on an even more important note, yo
On Jun 1 12:46, Ryan C. Underwood wrote:
>
> On Thu, May 31, 2012 at 04:01:43PM -0500, Ryan C. Underwood wrote:
> >
> > How can I "bisect" Cygwin i.e. by setting a certain date at which to
> > install packages that were current as of that date, and checking if
> > problem remains, so as to track
On Thu, May 31, 2012 at 04:01:43PM -0500, Ryan C. Underwood wrote:
>
> How can I "bisect" Cygwin i.e. by setting a certain date at which to
> install packages that were current as of that date, and checking if
> problem remains, so as to track down the date a problem/different
> behavior was intr
On Fri, Jun 01, 2012 at 10:28:09AM -0500, Thrall, Bryan wrote:
>
> See the "Old Update" from 8/5/2008 under
> http://www.fruitbat.org/Cygwin/index.html#cygwincirca: You need to
> specify -X when running Cygwin setup.exe.
Thanks, I'm not sure what about "Old Update" screamed "obsolete info"
to me
Ryan C. Underwood wrote on 2012-06-01:
> On Thu, May 31, 2012 at 11:51:53PM +0200, Cyrille Lefevre wrote:
>>
>> well, have you tryed the cygwin time machine :
>>
>> http://www.fruitbat.org/Cygwin/index.html#cygwincirca
>
> I must not be understanding how to use this. For example, if I take
> t
On Thu, May 31, 2012 at 11:51:53PM +0200, Cyrille Lefevre wrote:
>
> well, have you tryed the cygwin time machine :
>
> http://www.fruitbat.org/Cygwin/index.html#cygwincirca
I must not be understanding how to use this. For example, if I take
the URL for 2/13:
ftp://www.fruitbat.org/pub/cygwin/
On May 31 19:15, Ryan C. Underwood wrote:
>
> On Thu, May 31, 2012 at 11:51:53PM +0200, Cyrille Lefevre wrote:
> >
> > well, have you tryed the cygwin time machine :
> >
> > http://www.fruitbat.org/Cygwin/index.html#cygwincirca
>
> This indeed appears to be what I was looking for:
Better: Use
On Thu, May 31, 2012 at 11:51:53PM +0200, Cyrille Lefevre wrote:
>
> well, have you tryed the cygwin time machine :
>
> http://www.fruitbat.org/Cygwin/index.html#cygwincirca
This indeed appears to be what I was looking for:
The mirror I maintain contains every version of every package of
C
Le 31/05/2012 23:01, Ryan C. Underwood a écrit :
How can I "bisect" Cygwin i.e. by setting a certain date at which to
install packages that were current as of that date, and checking if
problem remains, so as to track down the date a problem/different
behavior was introduced sometime in the past
How can I "bisect" Cygwin i.e. by setting a certain date at which to
install packages that were current as of that date, and checking if
problem remains, so as to track down the date a problem/different
behavior was introduced sometime in the past year? Actually, if I
could start with the Cygwin
16 matches
Mail list logo
