Re: Call for testing Cygwin snapshot

2006-06-12 Thread Corinna Vinschen
On several days within the last few weeks, Yitzchak Scott-Thoennes wrote: > > Yes, removing the setsockopt calls from fdsock does get rsync working > > again. Sorry it took me so long to try. > > Still happening with 20060604. I disabled setting the buffers in CVS. What happens is that duplicat

Re: Call for testing Cygwin snapshot

2006-05-22 Thread Yitzchak Scott-Thoennes
On Wed, May 10, 2006 at 01:38:58AM -0400, Christopher Faylor wrote: > On Tue, May 09, 2006 at 10:30:50PM -0700, Yitzchak Scott-Thoennes wrote: > >On Tue, May 02, 2006 at 08:50:59PM -0700, Yitzchak Scott-Thoennes wrote: > >> On Tue, May 02, 2006 at 11:47:09AM -0400, Christopher Faylor wrote: > >> >

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Yitzchak Scott-Thoennes
On Wed, May 10, 2006 at 01:38:58AM -0400, Christopher Faylor wrote: > On Tue, May 09, 2006 at 10:30:50PM -0700, Yitzchak Scott-Thoennes wrote: > >On Tue, May 02, 2006 at 08:50:59PM -0700, Yitzchak Scott-Thoennes wrote: > >> On Tue, May 02, 2006 at 11:47:09AM -0400, Christopher Faylor wrote: > >> >

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Lloeki
>I don't know what this reg key does but there is no need to change it. >I switch around Cygwin DLLs all the time using simply the copy command >in CMD.EXE (with no Cygwin processes running of course) and have never >had to do anything else. Ditto. If this was really necessary, the information w

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Christopher Faylor
On Tue, May 09, 2006 at 11:56:06PM -0700, Brian Dessent wrote: >Lloeki wrote: >>Of course I just find it minutes after posting... >> >>it's in >>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer >>add a DWORD of name AlwaysUnloadDll and give it a 1. Though it's >>advertised eve

RE: Call for testing Cygwin snapshot

2006-05-10 Thread Dave Korn
On 10 May 2006 07:33, Lloeki wrote: >> there's even a reg key to tweak that flush delay >> but it seems I can't put the finger on it anymore. > > Of course I just find it minutes after posting... > > it's in > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer add a > DWORD of

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Lloeki
there's even a reg key to tweak that flush delay but it seems I can't put the finger on it anymore. Of course I just find it minutes after posting... it's in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer add a DWORD of name AlwaysUnloadDll and give it a 1. Though it's ad

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Brian Dessent
Lloeki wrote: > Of course I just find it minutes after posting... > > it's in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer > add a DWORD of name AlwaysUnloadDll and give it a 1. Though it's > advertised everywhere as managing all dlls, I dunno the exact effect, > and the

Re: Call for testing Cygwin snapshot

2006-05-10 Thread Jens Wilken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lloeki wrote: >> >> BTW: What's the easiest way to switch cygwin versions without >> having to reboot? I quite commonly come across changing snapshot >> dll's and having bash throw errors (probably relocation related >> or something of the sort) and i

Re: Call for testing Cygwin snapshot

2006-05-09 Thread Lloeki
BTW: What's the easiest way to switch cygwin versions without having to reboot? I quite commonly come across changing snapshot dll's and having bash throw errors (probably relocation related or something of the sort) and immediately return. After reboot it's fine. But what's a way to quickly swit

Re: Call for testing Cygwin snapshot

2006-05-09 Thread clayne
On Wed, May 10, 2006 at 01:38:58AM -0400, Christopher Faylor wrote: > Would you be willing to try building a cygwin DLL with Corinna's > > 2006-04-04 Corinna Vinschen <[EMAIL PROTECTED]> > > * net.cc (fdsock): Raise default SO_RCVBUF/SO_SNDBUF buffer sizes to > the same values

Re: Call for testing Cygwin snapshot

2006-05-09 Thread Christopher Faylor
On Tue, May 09, 2006 at 10:30:50PM -0700, Yitzchak Scott-Thoennes wrote: >On Tue, May 02, 2006 at 08:50:59PM -0700, Yitzchak Scott-Thoennes wrote: >> On Tue, May 02, 2006 at 11:47:09AM -0400, Christopher Faylor wrote: >> > On Mon, May 01, 2006 at 11:11:57PM -0700, Yitzchak Scott-Thoennes wrote: >>

Re: Call for testing Cygwin snapshot

2006-05-09 Thread Yitzchak Scott-Thoennes
On Tue, May 02, 2006 at 08:50:59PM -0700, Yitzchak Scott-Thoennes wrote: > On Tue, May 02, 2006 at 11:47:09AM -0400, Christopher Faylor wrote: > > On Mon, May 01, 2006 at 11:11:57PM -0700, Yitzchak Scott-Thoennes wrote: > > >On Mon, Apr 24, 2006 at 08:12:42PM +0200, Corinna Vinschen wrote: > > >> P

Re: Call for testing Cygwin snapshot

2006-05-02 Thread Christopher Faylor
On Tue, May 02, 2006 at 05:21:21PM +0100, Steven Hartland wrote: >Christopher Faylor wrote: >>On Mon, May 01, 2006 at 11:11:57PM -0700, Yitzchak Scott-Thoennes >>>I'm having problems with rsync'ing perl seeming to hang that didn't >>>happen with 1.5.18/9 or snapshots up to 20060329. I'll try to po

Re: Call for testing Cygwin snapshot

2006-05-02 Thread Steven Hartland
Christopher Faylor wrote: On Mon, May 01, 2006 at 11:11:57PM -0700, Yitzchak Scott-Thoennes I'm having problems with rsync'ing perl seeming to hang that didn't happen with 1.5.18/9 or snapshots up to 20060329. I'll try to post cygcheck output soon. Corinna changed ssh recently. Are you using

Re: Call for testing Cygwin snapshot

2006-05-02 Thread Christopher Faylor
On Mon, May 01, 2006 at 11:11:57PM -0700, Yitzchak Scott-Thoennes wrote: >On Mon, Apr 24, 2006 at 08:12:42PM +0200, Corinna Vinschen wrote: >> Please test the latest snapshot (at least 2006-Apr-24) from >> >> http://cygwin.com/snapshots/ >> >> Please report back in this thread when you encounte

Re: Call for testing Cygwin snapshot

2006-05-01 Thread Yitzchak Scott-Thoennes
On Mon, Apr 24, 2006 at 08:12:42PM +0200, Corinna Vinschen wrote: > Please test the latest snapshot (at least 2006-Apr-24) from > > http://cygwin.com/snapshots/ > > Please report back in this thread when you encounter a problem, which > you can't reproduce with 1.5.18 or 1.5.19. We're interest

Re: Call for testing Cygwin snapshot

2006-04-28 Thread Christopher Faylor
On Fri, Apr 28, 2006 at 10:22:58AM +0200, Danilo Turina wrote: >Christopher Faylor wrote: >>On Thu, Apr 27, 2006 at 03:38:27PM +0200, Danilo Turina wrote: >>>No, sorry: I'm not using a snapshot. I thought you intended to say that >>>/bin/pwd would have failed also with the current version. >> >>Th

Re: Call for testing Cygwin snapshot

2006-04-28 Thread Danilo Turina
Christopher Faylor wrote: On Thu, Apr 27, 2006 at 03:38:27PM +0200, Danilo Turina wrote: No, sorry: I'm not using a snapshot. I thought you intended to say that /bin/pwd would have failed also with the current version. Then please choose another thread to discuss any issues not involved with t

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Christopher Faylor
On Thu, Apr 27, 2006 at 03:38:27PM +0200, Danilo Turina wrote: >No, sorry: I'm not using a snapshot. I thought you intended to say that >/bin/pwd would have failed also with the current version. Then please choose another thread to discuss any issues not involved with the Cygwin snapshot. cgf -

Re: Call for testing Cygwin snapshot

2006-04-27 Thread mwoehlke
Dave Korn wrote: On 26 April 2006 20:21, Jerry D. Hedden wrote: In this case, I used the full 20060426 snapshot and generated some stuck processes. The output from 'ps' showed the following: PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 2944 11332 29292

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Eric Blake
Charles Wilson cwilson.fastmail.fm> writes: > > Nope, it was very consistent and did not change over time. One oddity is > that if you access a file (in a particular view (MVFS-speak for branch, > more or less)) via the 'multi-view' mount > > /cygdrive/m/my_view/my_VOB/some-path-to/some-file

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Eric Blake
Danilo Turina alcatel.it> writes: > > No, sorry: I'm not using a snapshot. I thought you intended to say that > /bin/pwd would have failed also with the current version. Here's the behavior I see in a dynamic view, under 5.94-5: $ /bin/pwd /cygdrive/l/Implementation $ cd script@@/main/ $ pwd

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Charles Wilson
Corinna Vinschen wrote: On Apr 25 00:42, Charles Wilson wrote: I'll take a look at this w.r.t clearcase. How exactly should I test -- what am I looking for? Just a little app that compares dirent.d_ino and stat.st_ino for a specified file on the strange filesystem? Thanks for the offer. C

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Danilo Turina
Eric Blake wrote: Another set of tests is to use the experimental coreutils-5.94-5. Doing/bin/pwd inside a directory on the strange filesystem stress tests d_ino (I already know that on ClearCase (MVFS), /bin/pwd fails inside of versioned directories, such as ccase/foo@@/main/, since ClearCase re

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Eric Blake
> > Another set of tests is to use the experimental coreutils-5.94-5. > > Doing/bin/pwd inside a directory on the strange filesystem stress tests > > d_ino (I already know that on ClearCase (MVFS), /bin/pwd fails inside of > > versioned directories, such as ccase/foo@@/main/, since ClearCase refuse

RE: Call for testing Cygwin snapshot

2006-04-27 Thread Dave Korn
On 26 April 2006 20:21, Jerry D. Hedden wrote: > In this case, I used the full 20060426 snapshot and generated some stuck > processes. The output from 'ps' showed the following: > > PIDPPIDPGID WINPID TTY UIDSTIME COMMAND > 2944 11332 29292? 78809

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Danilo Turina
Eric Blake wrote: [...] Another set of tests is to use the experimental coreutils-5.94-5. Doing/bin/pwd inside a directory on the strange filesystem stress tests d_ino (I already know that on ClearCase (MVFS), /bin/pwd fails inside of versioned directories, such as ccase/foo@@/main/, since ClearC

Re: Call for testing Cygwin snapshot

2006-04-27 Thread Corinna Vinschen
On Apr 26 17:19, Christopher Faylor wrote: > You've mentioned that the first failing snapshot was 2006-03-13 so I'm > working under the impression that your report was accurate. > > Neither Corinna nor I have been able to duplicate this hang. I'm running the cron job every 5 minutes overnight and

Re: Call for testing Cygwin snapshot

2006-04-26 Thread Christopher Faylor
On Wed, Apr 26, 2006 at 12:20:30PM -0700, Jerry D. Hedden wrote: >While I was watching the tumbleweeds blow by, I did some more >investigation on the problems I've been encountering with snapshots. >First of all, I tested every snapshot (always the FULL snapshot, of >course) Actually, installing

RE: Call for testing Cygwin snapshot

2006-04-26 Thread Jerry D. Hedden
While I was watching the tumbleweeds blow by, I did some more investigation on the problems I've been encountering with snapshots. First of all, I tested every snapshot (always the FULL snapshot, of course) from 2006-03-09 onwards with the following results: 20060309 - Last non-problematic snapsh

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Christopher Faylor
On Tue, Apr 25, 2006 at 06:53:00PM -0400, Larry Hall (Cygwin) wrote: >I looked at the differences and I think the problem is due to one of >them. Yep, no doubt about it. There's got to be a change in there >that's the cause of this problem. Thanks for narrowing it down, Larry. That really helps

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Larry Hall (Cygwin)
Christopher Faylor wrote: On Tue, Apr 25, 2006 at 10:17:47PM +0100, Dave Korn wrote: On 25 April 2006 21:43, Jerry D. Hedden wrote: Ernie Coskrey wrote: it's possible that Jerry has found a scenario that causes this problem to occur. Maybe not, but if he can reproduce it it would be worth che

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Christopher Faylor
On Tue, Apr 25, 2006 at 10:17:47PM +0100, Dave Korn wrote: >On 25 April 2006 21:43, Jerry D. Hedden wrote: > >> Ernie Coskrey wrote: >>> it's possible that Jerry has found a scenario that causes this problem to >>> occur. Maybe not, but if he can reproduce it it would be worth checking. >> >> I ca

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Dave Korn
On 25 April 2006 21:43, Jerry D. Hedden wrote: > Ernie Coskrey wrote: >> it's possible that Jerry has found a scenario that causes this problem to >> occur. Maybe not, but if he can reproduce it it would be worth checking. > > I can reproduce the problem. That's not the issue. I cannot provide

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Ernie Coskrey
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > Of Christopher Faylor > Sent: Tuesday, April 25, 2006 4:39 PM > To: cygwin@cygwin.com > Subject: Re: Call for testing Cygwin snapshot > > > On Tue, Apr 25, 2006 at 04:33:3

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Shankar Unni
Corinna Vinschen wrote: - The problem with Ctrl-C propagated to an unrelated child process (http://cygwin.com/ml/cygwin/2006-04/msg00556.html) should be fixed. Thanks. This also solved a problem we had with a nohup'ed background processing receiving SIGINT from the interactive shell from wh

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Jerry D. Hedden
Ernie Coskrey wrote: > it's possible that Jerry has found a scenario that causes this problem to > occur. > Maybe not, but if he can reproduce it it would be worth checking. I can reproduce the problem. That's not the issue. I cannot provide a little test app to produce the problem at will. As

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Christopher Faylor
On Tue, Apr 25, 2006 at 04:33:37PM -0400, Ernie Coskrey wrote: >Well, what I got from your message was that you were pretty sure that >your fix may have addressed the problem, but not 100% sure. That's why >I posted this follow-up; it's possible that Jerry has found a scenario >that causes this pr

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Ernie Coskrey
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > Of Christopher Faylor > Sent: Tuesday, April 25, 2006 4:26 PM > To: cygwin@cygwin.com > Subject: Re: Call for testing Cygwin snapshot > > > On Tue, Apr 25, 2006 at 03:37:4

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Christopher Faylor
dding this is just noise and helps increase the already incredible spam burden presented to the cygwin and (especially) postmaster mailing lists. >> Of Jerry D. Hedden >> Sent: Tuesday, April 25, 2006 9:27 AM >> To: cygwin ^^ >> Subject: RE: Call for testing Cygwin

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Ernie Coskrey
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > Of Jerry D. Hedden > Sent: Tuesday, April 25, 2006 9:27 AM > To: cygwin@cygwin.com > Subject: RE: Call for testing Cygwin snapshot > > > Jerry D. Hedden wrote: >

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Jerry D. Hedden
Jerry D. Hedden wrote: >I have a cron job (a bash script) that runs every 6 minutes, polling >and downloading info off the web. > >The problem is the script hangs at various places and the stuck >processes keep building up. > >Further, I have to kill these processes using the task monitor: kill >re

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Christopher Faylor
On Tue, Apr 25, 2006 at 06:27:17AM -0700, Jerry D. Hedden wrote: >Jerry D. Hedden wrote: >>I have a cron job (a bash script) that runs every 6 minutes, polling >>and downloading info off the web. >> >>The problem is the script hangs at various places and the stuck >>processes keep building up. >> >

RE: Call for testing Cygwin snapshot

2006-04-25 Thread Jerry D. Hedden
Jerry D. Hedden wrote: >I have a cron job (a bash script) >that runs every 6 minutes, polling and downloading info off the web. > >The problem is the script hangs at various places and the stuck >processes keep building up. > >Further, I have to kill these processes using the task monitor: kill >

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Charles Wilson on 4/24/2006 10:42 PM: > Corinna Vinschen wrote: > >> - Reintroducing the dirent member d_ino. 1.5.20 tries hard to return a >> useful d_ino value, which is supposed to be also the same as st_ino as >> returned by stat

Re: Call for testing Cygwin snapshot

2006-04-25 Thread Corinna Vinschen
On Apr 25 00:42, Charles Wilson wrote: > Corinna Vinschen wrote: > > >- Reintroducing the dirent member d_ino. 1.5.20 tries hard to return a > > useful d_ino value, which is supposed to be also the same as st_ino as > > returned by stat(2) in all cases, regardless of the obstacles to do > > th

Re: Call for testing Cygwin snapshot

2006-04-24 Thread Charles Wilson
Corinna Vinschen wrote: - Reintroducing the dirent member d_ino. 1.5.20 tries hard to return a useful d_ino value, which is supposed to be also the same as st_ino as returned by stat(2) in all cases, regardless of the obstacles to do this on Windows. Do you have strange file systems like

Re: Call for testing Cygwin snapshot

2006-04-24 Thread Angelo Graziosi
Corinna Vinschen wrote: > The problem with Ctrl-C propagated to an unrelated child process > (http://cygwin.com/ml/cygwin/2006-04/msg00556.html) should be fixed. It seems fixed in 20060421 and in 20060424 snapshots. Thanks a lot, Angelo. -- Unsubscribe info: http://cygwin.com/ml/

Re: Call for testing Cygwin snapshot

2006-04-24 Thread Christopher Faylor
On Mon, Apr 24, 2006 at 01:53:39PM -0700, Jerry D. Hedden wrote: >Corinna Vinschen wrote: >>It's time again to release a new Cygwin version. >> >>We're on the way to 1.5.20, and we're hoping that this release solves >>or at least workarounds a couple of problems introduced in earlier >>versions. P

RE: Call for testing Cygwin snapshot

2006-04-24 Thread Jerry D. Hedden
Corinna Vinschen wrote: > It's time again to release a new Cygwin version. > > We're on the way to 1.5.20, and we're hoping that this release solves > or at least workarounds a couple of problems introduced in earlier > versions. Seems to have created some new ones. I have a cron job (a bash scr

Call for testing Cygwin snapshot

2006-04-24 Thread Corinna Vinschen
Hi, it's time again to release a new Cygwin version. We're on the way to 1.5.20, and we're hoping that this release solves or at least workarounds a couple of problems introduced in earlier versions. 1.5.20 is mainly supposed to be a bugfix release. A couple of changes we're especially interest

[OT] Quoting characters (was: Re: Call for testing Cygwin snapshot)

2005-12-22 Thread Buzz
Op Thu, 22 Dec 2005 10:05:05 +0100 schreef Holger Krull in <43AA6C41.9080508gmx.de>: [``strange quoting''?] : But i believe folks will call this OT now. So do I. Read my slightly more topical response on the talk-list. L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of tr

Re: Call for testing Cygwin snapshot

2005-12-22 Thread Holger Krull
Buzz schrieb: Op Wed, 21 Dec 2005 20:54:12 +0100 schreef Holger Krull in <43A9B2E4.5080908gmx.de>: : Bas van Gompel schrieb: : > What do you mean when you write: ``strange quoting''? : > : Most likely he means your use of two single qoutes ' instead of one double ". To not get confused with (C

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Buzz
Op Wed, 21 Dec 2005 00:46:48 -0500 schreef Christopher Faylor in <[EMAIL PROTECTED]>: : On Wed, Dec 21, 2005 at 05:16:34AM +0100, Bas van Gompel wrote: [With a freshly built dll from a CVS-checkout on Dec 20. extra consoles pop up when logging into sshd on w95] You fixed it. Great. L8r, Buzz [

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Brian Dessent
Buzz wrote: > Those <`> are called back-ticks... (and there is nothing arbitrary > about my use of them, IMHO.) > > I did accidently start my quotes with <''>, not <``>. Sorry about that. On that topic I happen to agree with Markus Kuhn that ascii 0x60 should not be used in place of quotation ma

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Buzz
Op Wed, 21 Dec 2005 20:54:12 +0100 schreef Holger Krull in <43A9B2E4.5080908gmx.de>: : Bas van Gompel schrieb: : : > : > What do you mean when you write: ``strange quoting''? : > : : Most likely he means your use of two single qoutes ' instead of one double ". To not get confused with (C- or she

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Christopher Faylor
On Wed, Dec 21, 2005 at 08:54:12PM +0100, Holger Krull wrote: >Bas van Gompel schrieb: >>What do you mean when you write: ``strange quoting''? > >Most likely he means your use of two single qoutes ' instead of one >double ". And the arbitrary use of ticks ` Exactly. Thank you for clarifying this

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Holger Krull
Bas van Gompel schrieb: What do you mean when you write: ``strange quoting''? Most likely he means your use of two single qoutes ' instead of one double ". And the arbitrary use of ticks ` -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwi

Re: Call for testing Cygwin snapshot

2005-12-21 Thread Bas van Gompel
Op Wed, 21 Dec 2005 00:46:48 -0500 schreef Christopher Faylor in <[EMAIL PROTECTED]>: : On Wed, Dec 21, 2005 at 05:16:34AM +0100, Bas van Gompel wrote: [Testing freshly built from a CVS-checkout on Dec 20...] : > This is on win 95 again... : > I commonly source a file containing among other thin

Re: Call for testing Cygwin snapshot

2005-12-20 Thread Christopher Faylor
On Wed, Dec 21, 2005 at 05:16:34AM +0100, Bas van Gompel wrote: >Op Wed, 30 Nov 2005 18:11:37 +0100 schreef Corinna Vinschen >in <20051130171137.GE2999calimero.vinschen.de>: > >: ask people for testing the latest snapshot, 2005-Nov-30, from > >Actually, this is freshly built from a CVS-checkout on

Re: Call for testing Cygwin snapshot

2005-12-20 Thread Bas van Gompel
Op Wed, 30 Nov 2005 18:11:37 +0100 schreef Corinna Vinschen in <20051130171137.GE2999calimero.vinschen.de>: : ask people for testing the latest snapshot, 2005-Nov-30, from Actually, this is freshly built from a CVS-checkout on Dec 20. : Please report back in this thread when you encounter a pr

Re: Call for testing Cygwin snapshot

2005-12-19 Thread David Rothenberger
On 12/8/2005 4:08 PM, David Rothenberger wrote: -- Problem 2: -- This is also with XEmacs. I normally start XEmacs with the following command from a CMD.EXE shel

Re: Call for testing Cygwin snapshot (rsync mem use)

2005-12-19 Thread Corinna Vinschen
On Dec 18 08:56, David Rothenberger wrote: > Using the --delete switch to rsync with a large number of files causes > the rsync process to use large amounts of virtual memory with recent > snapshots, including 20051216. With a DLL built from CVS on 20051110, > this doesn't happen. > > The easie

Re: Call for testing Cygwin snapshot (d_ino)

2005-12-18 Thread Larry Hall (Cygwin)
Angelo Graziosi wrote: I wrote: The code that causes this error should be : --- #if defined(_POSIX_SOURCE) // Posix does not require that the d_ino field be present, and some // systems do not provide it. # define REAL_DIR_ENTRY(dp) 1 #else # define

Re: Call for testing Cygwin snapshot (d_ino)

2005-12-18 Thread Angelo Graziosi
I wrote: > The code that causes this error should be : > > --- > #if defined(_POSIX_SOURCE) > // Posix does not require that the d_ino field be present, and some > // systems do not provide it. > # define REAL_DIR_ENTRY(dp) 1 > #else > # define REAL_DI

Re: Call for testing Cygwin snapshot (d_ino)

2005-12-18 Thread Christopher Faylor
On Sun, Dec 18, 2005 at 11:22:33PM +0100, Angelo Graziosi wrote: > >Christopher Faylor wrote: >> >>> Angelo Graziosi wrote: >>> >>> >>> I built ROOT-5.06.00, a CERN application, at Nov 10 2005 using >>> GCC-3.3.3-3 and the snapshot of that time. >>> >>> All worked fine. >>> >>> Now I have repeate

Re: Call for testing Cygwin snapshot (d_ino)

2005-12-18 Thread Angelo Graziosi
Christopher Faylor wrote: > >> Angelo Graziosi wrote: >> >> >> I built ROOT-5.06.00, a CERN application, at Nov 10 2005 using >> GCC-3.3.3-3 and the snapshot of that time. >> >> All worked fine. >> >> Now I have repeated the build using the same method, the same >> GCC-3.3.3-3, but with the cur

Re: Call for testing Cygwin snapshot

2005-12-18 Thread Christopher Faylor
On Sun, Dec 18, 2005 at 12:55:47PM +0100, Angelo Graziosi wrote: >The build fails: > >--- >unix/src/TUnixSystem.cxx: In static member function `static const char* > TUnixSystem::UnixGetdirentry(void*)': >unix/src/TUnixSystem.cxx:3388: error: 'struct dirent

Re: Call for testing Cygwin snapshot (rsync mem use)

2005-12-18 Thread David Rothenberger
Using the --delete switch to rsync with a large number of files causes the rsync process to use large amounts of virtual memory with recent snapshots, including 20051216. With a DLL built from CVS on 20051110, this doesn't happen. The easiest way I found to reproduce it was to run the command:

Re: Call for testing Cygwin snapshot

2005-12-18 Thread Angelo Graziosi
I built ROOT-5.06.00, a CERN application, at Nov 10 2005 using GCC-3.3.3-3 and the snapshot of that time. All worked fine. Now I have repeated the build using the same method, the same GCC-3.3.3-3, but with the current snapshot 20051216 23:59:19. The build fails: -

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix..binutils issue)

2005-12-16 Thread Peter Rehley
On Dec 16, 2005, at 7:05 PM, Christopher Faylor wrote: On Fri, Dec 16, 2005 at 06:54:48PM -0800, Peter Rehley wrote: I know that the cygwin getopt and libiberty getopt are different, but I was just wondering why there is a liberty directory in the cygwin src. Because the cygwin DLL build u

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix..binutils issue)

2005-12-16 Thread Christopher Faylor
On Fri, Dec 16, 2005 at 06:54:48PM -0800, Peter Rehley wrote: >I know that the cygwin getopt and libiberty getopt are different, but >I was just wondering why there is a liberty directory in the cygwin src. Because the cygwin DLL build uses libiberty. What other reason would there be? >And fin

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix..binutils issue)

2005-12-16 Thread Peter Rehley
On Dec 16, 2005, at 6:14 PM, Christopher Faylor wrote: On Fri, Dec 16, 2005 at 05:50:01PM -0800, Peter Rehley wrote: On Dec 16, 2005, at 3:41 PM, Christopher Faylor wrote: On Fri, Dec 16, 2005 at 02:41:54PM -0800, Peter Rehley wrote: I just noticed something else that may or may not be a prob

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix..binutils issue)

2005-12-16 Thread Christopher Faylor
On Fri, Dec 16, 2005 at 05:50:01PM -0800, Peter Rehley wrote: >On Dec 16, 2005, at 3:41 PM, Christopher Faylor wrote: >>On Fri, Dec 16, 2005 at 02:41:54PM -0800, Peter Rehley wrote: >>>I just noticed something else that may or may not be a problem (noticed >>>when working on tftpd). When I link wi

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix..binutils issue)

2005-12-16 Thread Peter Rehley
On Dec 16, 2005, at 3:41 PM, Christopher Faylor wrote: On Fri, Dec 16, 2005 at 02:41:54PM -0800, Peter Rehley wrote: I just noticed something else that may or may not be a problem (noticed when working on tftpd). When I link with iberty (-liberty), the getopt function doesn't return the corre

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix)

2005-12-16 Thread Christopher Faylor
On Fri, Dec 16, 2005 at 02:41:54PM -0800, Peter Rehley wrote: >I just noticed something else that may or may not be a problem >(noticed when working on tftpd). When I link with iberty (-liberty), >the getopt function doesn't return the correct value for the option >argument. Here is a sampl

Re: Call for testing Cygwin snapshot (getopt and -liberty don't mix)

2005-12-16 Thread Peter Rehley
Hi, I just noticed something else that may or may not be a problem (noticed when working on tftpd). When I link with iberty (-liberty), the getopt function doesn't return the correct value for the option argument. Here is a sample program #include #include int main (int argc, char *a

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-14 Thread Corinna Vinschen
On Dec 13 22:16, Angelo Graziosi wrote: > > > Dr. Volker Zell wrote: > > > > > I just checked this with 20051212 and emacs (not xemacs). > > > > emacs -q > > > > M-x flyspell-mode > > M-x compile > > M-x recompile > > > > For me everything is working fine here. > > > > > I have tried also with

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-13 Thread Angelo Graziosi
Dr. Volker Zell wrote: > > I just checked this with 20051212 and emacs (not xemacs). > > emacs -q > > M-x flyspell-mode > M-x compile > M-x recompile > > For me everything is working fine here. > I have tried also with the snapshots 20051212 13:44:06, 20051213 00:12:38 with the same problems:

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-13 Thread Dr. Volker Zell
> Angelo Graziosi writes: > With the snapshots 20051212 13:44:06 the problems described previously > remain. > They seem a little worst. I just checked this with 20051212 and emacs (not xemacs). emacs -q M-x flyspell-mode M-x compile M-x recompile For me everything is working

Re: Call for testing Cygwin snapshot

2005-12-12 Thread Peter Rehley
Hi, With the 20051212 snapshot I am not seeing this problem. I'm still running tests, but at this point it looks good. I'm also still trying to see if it will hang. Peter On Dec 7, 2005, at 3:18 PM, Peter Rehley wrote: Hi, I've retried the problem I mentioned in this thread http:// c

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Angelo Graziosi
With the snapshots 20051212 13:44:06 the problems described previously remain. They seem a little worst. Best regards, Angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.c

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Dr. Volker Zell
> Corinna Vinschen writes: > You *did* read that I checked in a patch this morning which should solve > this, didn't you? > http://cygwin.com/ml/cygwin/2005-12/msg00452.html Yup, xemacs can start subprocesses again with the 20051212 snapshot. > Corinna Thanks Volker -

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Angelo Graziosi
Dr. Volker Zell wrote: > > I think the OP means emacs and not xemacs. > Yes, I mean EMACS and not XEmacs! I confirm that the problems described in http://cygwin.com/ml/cygwin/2005-12/msg00441.html are absent with the snapshot 2005.10.24. Ciao, angelo. -- Unsubscribe info: ht

Re: Call for testing Cygwin snapshot

2005-12-12 Thread David Rothenberger
On 12/12/2005 1:00 PM, Corinna Vinschen wrote: > On Dec 12 11:59, David Rothenberger wrote: >> On 12/12/2005 2:32 AM, Corinna Vinschen wrote: >> 3. XEmacs will prompt for a command. The prompt will already have >>"grep -n ". Just add (without quotes) "-i system /etc/passwd" and >>then pre

Re: Call for testing Cygwin snapshot

2005-12-12 Thread Christopher Faylor
On Mon, Dec 12, 2005 at 10:00:39PM +0100, Corinna Vinschen wrote: >On Dec 12 11:59, David Rothenberger wrote: >> On 12/12/2005 2:32 AM, Corinna Vinschen wrote: >> > But I can't reproduce this grep problem since I'm unable to start the >> > above grep. The grep submenu is entirely greyed out when I

Re: Call for testing Cygwin snapshot

2005-12-12 Thread Corinna Vinschen
On Dec 12 11:59, David Rothenberger wrote: > On 12/12/2005 2:32 AM, Corinna Vinschen wrote: > > But I can't reproduce this grep problem since I'm unable to start the > > above grep. The grep submenu is entirely greyed out when I look into > > it. > > I didn't mention the grep submenu. Here's a

Re: Call for testing Cygwin snapshot

2005-12-12 Thread David Rothenberger
On 12/12/2005 2:32 AM, Corinna Vinschen wrote: > On Dec 8 16:08, David Rothenberger wrote: >> -- >> Problem 2: >> -- >> This is also with XEmacs. I normally start

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Corinna Vinschen
On Dec 12 13:32, Dr. Volker Zell wrote: > > Corinna Vinschen writes: > > > Could the xemacs maintainer please have a look into that and break > > this down into something which can be handled by a xemacs ignorant? > > I think the OP means emacs and not xemacs. But xemacs has problems

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Dr. Volker Zell
> Corinna Vinschen writes: > Could the xemacs maintainer please have a look into that and break > this down into something which can be handled by a xemacs ignorant? I think the OP means emacs and not xemacs. But xemacs has problems with starting subprocesses as indicated in o http:

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-12 Thread Corinna Vinschen
On Dec 11 22:44, Angelo Graziosi wrote: > > > The problems described in > >http://cygwin.com/ml/cygwin/2005-12/msg00441.html > > are absent if one uses the snapshot 2005.10.24 12:04:00. > > Those problems appear at least from the snapshot 2005.11.17 and are > present also with the last sna

Re: Call for testing Cygwin snapshot

2005-12-12 Thread Corinna Vinschen
On Dec 8 16:08, David Rothenberger wrote: > -- > Problem 1: > -- > With the 20051207 snapshot, I'm getting > recreate_mmaps_after_fork_failed errors from XEmacs.

Re: Call for testing Cygwin snapshot(was: Emacs and 'alarm clock')

2005-12-11 Thread Angelo Graziosi
The problems described in http://cygwin.com/ml/cygwin/2005-12/msg00441.html are absent if one uses the snapshot 2005.10.24 12:04:00. Those problems appear at least from the snapshot 2005.11.17 and are present also with the last snapshot 2005.12.10. [With the recent snapshots some commands

Re: Call for testing Cygwin snapshot

2005-12-10 Thread Dr. Volker Zell
> Corinna Vinschen writes: > Since we're much too long on the way to the 1.5.19 release and there > are already way too many changes since 1.5.18, we would again like to > ask people for testing the latest snapshot, 2005-Nov-30, from > http://www.cygwin.com/snapshots/ >

Re: Call for testing Cygwin snapshot

2005-12-08 Thread David Rothenberger
I'm having three problems with the latest snapshot. -- Problem 1: -- With the 20051207 snapshot, I'm getting recreate_mmaps_after_fork_failed errors from XEmacs.

Re: Call for testing Cygwin snapshot

2005-12-08 Thread Yitzchak Scott-Thoennes
On Wed, Nov 30, 2005 at 06:11:37PM +0100, Corinna Vinschen wrote: > 1.5.19 has also some new functionality over 1.5.18. If you have sources > which take advantage of that stuff if present, we're also interested in > getting feeedback about those: > > - clock_getres, clock_setres. > - fts(3) f

Re: Call for testing Cygwin snapshot

2005-12-05 Thread Buzz
Op Sun, 4 Dec 2005 22:51:38 +0100 schreef Corinna Vinschen in <20051204215138.GA24677calimero.vinschen.de>: : On Dec 2 23:25, Bas van Gompel wrote: : > Op Fri, 2 Dec 2005 11:40:49 +0100 schreef Corinna Vinschen : > [gethostbyname on w95] [...] : I applied a fix to CVS. FYI, the $windir environ

Re: Call for testing Cygwin snapshot (problem with getline?)

2005-12-05 Thread Brian Dessent
Nenad Antic wrote: > Actually, I didn't mean that this happens only when building vith > mod_perl (event though that's how if ran into it). It happens when > configuring apache (1.33 and 1.34, at least), even with the fixes that > exist in the cygwin packages. AFAIK apache builds fine on linux (di

Re: Call for testing Cygwin snapshot (problem with getline?)

2005-12-05 Thread Nenad Antic
Corinna Vinschen wrote, on 12/5/2005 11:19 AM: On Dec 5 11:06, Nenad Antic wrote: Corinna Vinschen wrote, on 11/30/2005 6:11 PM: 1.5.19 has also some new functionality over 1.5.18. If you have sources which take advantage of that stuff if present, we're also interested in getting fe

  1   2   >