RE: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-08 Thread Rob Burgers
Hi, Same here. Everything is working fine now. Thanks a lot for the support. Happy Cygwin, Rob > > Thanks for the test case. This was due to Cygwin's not dealing well > with Windows reuse of pids. > > It should be fixed in today's snapshot when it shows up at: > > http://cygwin.com/snapshots/

Re: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-08 Thread marco atzeri
On 5/8/2012 5:11 PM, Christopher Faylor wrote: Thanks for the test case. This was due to Cygwin's not dealing well with Windows reuse of pids. It should be fixed in today's snapshot when it shows up at: http://cygwin.com/snapshots/ cgf confirmed Thanks Marco -- Pr

Re: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-08 Thread Christopher Faylor
On Tue, May 08, 2012 at 01:50:21PM +0200, Rob Burgers wrote: >Hi Christopher, > >I managed to create a simple replicator for the latest issue with the >2012-05-07 snapshot. > >The script below crashes within seconds with the 'Resource temporarily >unavailable' message. > > >f.

Re: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-08 Thread marco atzeri
On 5/8/2012 1:50 PM, Rob Burgers wrote: Hi Christopher, I managed to create a simple replicator for the latest issue with the 2012-05-07 snapshot. The script below crashes within seconds with the 'Resource temporarily unavailable' message. f.sh: #!/b

RE: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-08 Thread Rob Burgers
Hi Christopher, I managed to create a simple replicator for the latest issue with the 2012-05-07 snapshot. The script below crashes within seconds with the 'Resource temporarily unavailable' message. f.sh: #!/bin/bash cmd /C start notepad while ( tru

RE: Please try latest snapshot (was Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process)

2012-05-07 Thread Rob Burgers
Hi Christopher, Thanks a lot for your concern and for the patch. Everything appeared to be okay at first glance when applying it to the test applications. However there might be some regression issue still: When I used it against our application that originally triggered the issue I got error m

Re: please try latest snapshot

2005-09-09 Thread Christopher Faylor
On Fri, Sep 09, 2005 at 05:06:30PM -0700, David Rothenberger wrote: >I'm having a problem with the 20050908 snapshot. I have been using >my own compiled version of XEmacs 21.4 for some time and I >frequently use the DDE client winclient. I noticed that this client >started core dumping with recent

Re: please try latest snapshot

2005-09-09 Thread David Rothenberger
I'm having a problem with the 20050908 snapshot. I have been using my own compiled version of XEmacs 21.4 for some time and I frequently use the DDE client winclient. I noticed that this client started core dumping with recent snapshots. I did some investigation and found that winclient uses WinMa

Re: please try latest snapshot

2005-08-24 Thread Christopher Faylor
On Wed, Aug 24, 2005 at 06:05:31PM +, Eric Blake wrote: >I'm having a problem with the 20050824 snapshot. execl() and friends >are in violation of POSIX, which requires EACCESS (pathname is not >regular file and cannot be executed) or ENOEXEC (pathname is not >executable image, although it has

Re: please try latest snapshot

2005-08-24 Thread Christopher Faylor
On Wed, Aug 24, 2005 at 09:48:42AM -0700, David Rothenberger wrote: Content-Description: message body and .signature >I'm having a problem with the 20050824 snapshot. Running "procps -ef" >displays "" for all processes except for procps. > >% procps -ef >UIDPID PPID C STIME TTY T

Re: please try latest snapshot

2005-08-24 Thread David Rothenberger
I'm having a problem with the 20050824 snapshot. Running "procps -ef" displays "" for all processes except for procps. % procps -ef UIDPID PPID C STIME TTY TIME CMD drothe6932 1 0 09:26 tty0 00:00:01 drothe7592 6932 1 09:26 tty0 00:00:04 drothe4848

Re: please try latest snapshot

2005-08-22 Thread Christopher Faylor
On Mon, Aug 22, 2005 at 02:18:56PM -0400, Christopher Faylor wrote: >We're heading into a cygwin 1.5.19 release so it is time for a thorough >testing of the latest snapshot. > >http://cygwin.com/ Urgh. Make that: http://cygwin.com/snapshots/ Also please mention the date of the snapshot that you

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-06 Thread Brian Dessent
Arash Partow wrote: > What kernel version and what NPTL version do you have installed? Kernel version 2.6.10 and glibc 2.3.2 as packaged by Debian unstable. I don't know whether they configure glibc for LinuxThreads or NPTL for this package. Under FreeBSD-5.4 I get the following: $ ./example1

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-06 Thread Arash Partow
Hi Brian, What kernel version and what NPTL version do you have installed? Kind regards Arash Partow __ Be one who knows what they don't know, Instead of being one who knows not what they don't know, Thinking they know everything about all thi

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-05 Thread Brian Dessent
Arash Partow wrote: > I've done a clean install of cygwin with dll 1.5.18 and also tried > snapshots from 2nd, 4th and 5th. Unfortunetly issues relating to > threading and memory leaks as described in the following post - still > exists: > > http://sources.redhat.com/ml/cygwin/2005-06/msg00186.ht

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-05 Thread Christopher Faylor
On Wed, Jul 06, 2005 at 04:17:34AM +, Arash Partow wrote: >I have the mutex set to default mode, and after a few seconds of the >test running mutexes locking unlocking, all of a sudden the mutexes >stop locking, and basically report back EBUSY from pthread_mutex_lock. The message that you are

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-05 Thread Arash Partow
Hi Chris, Actually things are getting slightly worse, basically same test scenario (not the full blown app you keep on mentioning), but this time mutex locks are failing + the ye-olde massive memory leaks. I have the mutex set to default mode, and after a few seconds of the test running mutexes

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-05 Thread Christopher Faylor
On Wed, Jul 06, 2005 at 01:36:54AM +, Arash Partow wrote: >I've done a clean install of cygwin with dll 1.5.18 and also tried >snapshots from 2nd, 4th and 5th. Unfortunetly issues relating to >threading and memory leaks as described in the following post - still >exists: > >http://sources.redh

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-05 Thread Arash Partow
Hi Chris, I've done a clean install of cygwin with dll 1.5.18 and also tried snapshots from 2nd, 4th and 5th. Unfortunetly issues relating to threading and memory leaks as described in the following post - still exists: http://sources.redhat.com/ml/cygwin/2005-06/msg00186.html Regards Ar

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-01 Thread Peter Rehley
Yeah, I tried the June 30th snapshot. On Jul 1, 2005, at 1:21 PM, Christopher Faylor wrote: On Fri, Jul 01, 2005 at 01:09:21PM -0700, Peter Rehley wrote: My tests indicated that the changes are working correctly. You did try the snapshot, right? I neglected to mention that I had to make some

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-01 Thread Christopher Faylor
On Fri, Jul 01, 2005 at 04:21:20PM -0400, Christopher Faylor wrote: >On Fri, Jul 01, 2005 at 01:09:21PM -0700, Peter Rehley wrote: >>My tests indicated that the changes are working correctly. > >You did try the snapshot, right? I neglected to mention that I had to >make some corresponding changes

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-01 Thread Christopher Faylor
On Fri, Jul 01, 2005 at 01:09:21PM -0700, Peter Rehley wrote: >My tests indicated that the changes are working correctly. You did try the snapshot, right? I neglected to mention that I had to make some corresponding changes to the DLL beyond the below changes. I don't know exactly when I did that

Re: Please try latest snapshot -- pthreads mutex users please note

2005-07-01 Thread Peter Rehley
My tests indicated that the changes are working correctly. Peter On Jun 30, 2005, at 8:23 PM, Christopher Faylor wrote: We're coming close to a 1.5.18 release. Please try the latest snapshot at http://cygwin.com/snapshots/ and help verify that there are no regresions against 1.5.17. I'm part

Re: Please try latest snapshot (Volker?)

2004-07-20 Thread Dr. Volker Zell
> Christopher Faylor writes: > My problem building cygserver seems to be fixed in the lastest > snapshot. > Volker could you confirm that the problem with cygserver is no > longer present in the latest snapshot? Yes I can confirm, that the problem with cygserver is fixed in c

RE: Please try latest snapshot - 1.5.3 soon

2003-08-30 Thread Gary R. Van Sickle
> The latest snapshot should be close to cygwin 1.5.3. It fixes a recent > problem with nested signals. Maybe a strange coincidence, but CTRL-C seems to stop wget a whole heck of a lot quicker now. -- Gary R. Van Sickle Brewer. Patriot. -- Unsubscribe info: http://cygwin.com/ml/#unsubscr

RE: Please try latest snapshot

2002-11-22 Thread D. N. Knisely
Spoke too soon; latest snapshot is much better with UW imapd and Outlook/IMAP (i.e., doesn't hang 100%), but still hangs every 10 minutes or so. Seems to be a less likely race condition problem or something. >FWIW (quite a lot to me, actually), my mysterious UW imapd hanging problem >went away wi

RE: Please try latest snapshot

2002-11-22 Thread D. N. Knisely
: Please try latest snapshot On Thu, Nov 21, 2002 at 11:47:22PM -0500, Christopher Faylor wrote: >I'm regenerating a snapshot right now which may become 1.3.16. >Please try it. Please try the later of a 2002-11-21 or 2002-11-22 >snapshot. > >FWIW, I was able to duplicate the

Re: Please try latest snapshot

2002-11-22 Thread Jonathan Fosburgh
On Thursday 21 November 2002 10:47 pm, you wrote: > I'm regenerating a snapshot right now which may become 1.3.16. > Please try it. Please try the later of a 2002-11-21 or 2002-11-22 > snapshot. > The problems earlier reported with TinyFugue persist in the 11/21 snapshot. -- Unsubscribe info:

Re: Please try latest snapshot

2002-11-21 Thread Christopher Faylor
On Thu, Nov 21, 2002 at 11:47:22PM -0500, Christopher Faylor wrote: >I'm regenerating a snapshot right now which may become 1.3.16. >Please try it. Please try the later of a 2002-11-21 or 2002-11-22 >snapshot. > >FWIW, I was able to duplicate the "emacs hangs if you resize the screen" >problem twi