Re: mbrtowc bug

Corinna Vinschen cygwin.com> writes: > > > > I'm running the testcase on XP SP3. I have an idea why it fails for > > > > you. The eucJP codepage 20932 is not installed by default on US and > > > > other western language systems by default up to Windows 2003. What you > > > > have to do is, ope

Re: MVFS results

Corinna Vinschen cygwin.com> writes: > > Or maybe this is a case where we need a FlushFileBuffer call during the > > utimens_fs after all, in addition to closing the duplicate descriptor, so that > > the original handle no longer has any state that needs flushing which might > > inadvertently

[ANNOUNCEMENT] [1.7] Updated: rebase-3.0.1-1

New News: === I have updated the version of rebase to 3.0.1-1. The tarballs should be available on a Cygwin mirror near you shortly. The only change since the previous release is: * Change rebaseall to allow rebasing under dash too. Old News: === The Cygwin rebase package original

Re: MVFS results

On Jul 20 16:58, Eric Blake wrote: > Corinna Vinschen cygwin.com> writes: > > + InitializeObjectAttributes (&attr, &ro_u_empty, > > pc.objcaseinsensitive > (), > > + fh, NULL); > > Yet the obvious fix of using get_handle() instead of fh doesn't help either. O

Re: MVFS results

Corinna Vinschen cygwin.com> writes: > Just to be sure. This does not occur with cp -p on other filesystems > than MVFS, right? I don't see that problem on NTFS or FAT. I can confirm that with both NTFS and FAT, the NtSetInformationFile in utimens_fs is immediate (no fd has to be closed). Th

view/kill rdp sessions?

Is there a way to view/kill open RDP sessions in cygwin bash? Something like qwinsta/rwinsta but for cygwin? -- View this message in context: http://www.nabble.com/view-kill-rdp-sessions--tp24573603p24573603.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports

Re: mbrtowc bug

On Jul 20 14:31, Corinna Vinschen wrote: > On Jul 20 06:21, Eric Blake wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > According to Corinna Vinschen on 7/20/2009 6:08 AM: > > > I'm running the testcase on XP SP3. I have an idea why it fails for > > > you. The eucJP codepage

Re: MVFS results

On Jul 20 15:02, Eric Blake wrote: > Corinna Vinschen cygwin.com> writes: > > > Found the root cause. R/O vs. writeable.> > > It's not, unfortunately. There is no code path in Cygwin's utimens > > and friends which temorarily resets the R/O attribute. If the R/O > > attribute is actually remov

Re: MVFS results

Corinna Vinschen cygwin.com> writes: > > Found the root cause. R/O vs. writeable.> > It's not, unfortunately. There is no code path in Cygwin's utimens > and friends which temorarily resets the R/O attribute. If the R/O > attribute is actually removed temporarily, then touch calls chmod > or

Re: Re: FAQ question regarding tcl/tk and paths

On Tue, Jul 21, 2009 at 12:36:58AM +1000, Shaddy Baddah wrote: >At this point I am tempted to launch into *my* wishlist for tcltk, but I >wont. Thank you. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cy

Re: WCONTINUED/WIFCONTINUED

On Mon, Jul 20, 2009 at 04:08:09PM +0200, Reini Urban wrote: >2009/7/19 Christopher Faylor: >> On Fri, Jul 10, 2009 at 12:20:20PM -0400, Christopher Faylor wrote: >>>On Fri, Jul 10, 2009 at 09:49:59AM +0200, Reini Urban wrote: Any volunteer for WCONTINUED, WIFCONTINUED() for wait4() for the >>>

Re: Re: FAQ question regarding tcl/tk and paths

Hi Larry, Larry Hall (Cygwin) wrote: ? No? Dang! I've been looking for an appropriate place to use that phrase. I'll keep trying. ;-) YANMAA - You Are Not Mean At All ;-) You might have more luck looking in the context of 'insight'. 'insight' comes with th

Re: [1.7] fifo regression

On Mon, Jul 20, 2009 at 01:57:59PM +0200, Corinna Vinschen wrote: >On Jul 19 19:35, Christopher Faylor wrote: >> On Tue, Jul 07, 2009 at 02:02:12PM -0400, Christopher Faylor wrote: >> >On Mon, Jul 06, 2009 at 10:18:39PM -0400, Christopher Faylor wrote: >> >>On Mon, Jul 06, 2009 at 07:03:11AM -0600,

Re: WCONTINUED/WIFCONTINUED

2009/7/19 Christopher Faylor: > On Fri, Jul 10, 2009 at 12:20:20PM -0400, Christopher Faylor wrote: >>On Fri, Jul 10, 2009 at 09:49:59AM +0200, Reini Urban wrote: >>>Any volunteer for WCONTINUED, WIFCONTINUED() for wait4() for the >>>initial cygwin-1.7 release? >>>See http://www.opengroup.org/onlin

Re: mbrtowc bug

On Jul 20 06:21, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to Corinna Vinschen on 7/20/2009 6:08 AM: > > I'm running the testcase on XP SP3. I have an idea why it fails for > > you. The eucJP codepage 20932 is not installed by default on US and > > other w

Re: mbrtowc bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 7/20/2009 6:08 AM: > I'm running the testcase on XP SP3. I have an idea why it fails for > you. The eucJP codepage 20932 is not installed by default on US and > other western language systems by default up to Windows

Re: mbrtowc bug

On Jul 20 14:08, Corinna Vinschen wrote: > On Jul 20 05:59, Eric Blake wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > According to Corinna Vinschen on 7/20/2009 5:55 AM: > > > > > > What bug?!? When I run this testcase on Cygwin 1.7, it returns 0. What > > > is the suppose

Re: mbrtowc bug

On Jul 20 05:59, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to Corinna Vinschen on 7/20/2009 5:55 AM: > > > > What bug?!? When I run this testcase on Cygwin 1.7, it returns 0. What > > is the supposed error and what is expected if it's behaving correctly?

Re: mbrtowc bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 7/20/2009 5:55 AM: > > What bug?!? When I run this testcase on Cygwin 1.7, it returns 0. What > is the supposed error and what is expected if it's behaving correctly? Hmm. Here's what it did for me on Windows XP (m

Re: [1.7] fifo regression

On Jul 19 19:35, Christopher Faylor wrote: > On Tue, Jul 07, 2009 at 02:02:12PM -0400, Christopher Faylor wrote: > >On Mon, Jul 06, 2009 at 10:18:39PM -0400, Christopher Faylor wrote: > >>On Mon, Jul 06, 2009 at 07:03:11AM -0600, Eric Blake wrote: > >>>But on cygwin 1.7, when you attempt to create

Re: OpenSSH - sftp not working for non-Administrator users

On Jul 20 13:43, Thorsten Kampe wrote: > * Doug Lim (Mon, 20 Jul 2009 00:46:44 -0500) > > > The cygcheck.out file shows that the cygwin directory was in the > > > PATH when you ran the cygcheck program. It doesn't necessarily mean > > > that it is the path that a service sees. > > > > > I added

Re: sh.exe: TP_NUM_W_BUFS too small?

Corinna Vinschen cygwin.com> writes: > Yes, it is definitely a bug. AFAICS this occurs when a process forks > too deeply (child forks, grandchild forks again, etc, without execing). > The fork() setjmp/longjmp magic accidentally skipped the cleanup > destructor which is supposed to free the temp

Re: mbrtowc bug

On Jul 20 13:42, Corinna Vinschen wrote: > On Jul 20 05:15, Eric Blake wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > The gnulib unit tests are declaring that cygwin's mbrtowc is broken. STC: > > > > #include > > #include > > #include > > int main () > > { > > if (setl

Re: OpenSSH - sftp not working for non-Administrator users

* Doug Lim (Mon, 20 Jul 2009 00:46:44 -0500) > > The cygcheck.out file shows that the cygwin directory was in the > > PATH when you ran the cygcheck program. It doesn't necessarily mean > > that it is the path that a service sees. > > > I added D:\cygwin\bin to the PATH via the Environment Varia

Re: mbrtowc bug

On Jul 20 05:15, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > The gnulib unit tests are declaring that cygwin's mbrtowc is broken. STC: > > #include > #include > #include > int main () > { > if (setlocale (LC_ALL, "ja_JP.eucJP") != NULL) > { > char input

Re: sh.exe: TP_NUM_W_BUFS too small?

On Jul 20 09:37, Magnus Holmgren wrote: > When running configure scripts, I sometimes see this error message repeated > several times, for different lines of the configure script: > > bin\sh.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. > > I saw this when building libsdl 1.2.13

Re: gcc-3 problem when compiling

Thomas Steinbach wrote: Hi Thomas, glad to hear you got your install working again. We'll probably never know quite what happened there, but with any luck you'll never need to. > btw: In my old (gcc3) makefile I used -mno-cygwin within the > LDFLAGS to compile real native win32 executables, bu

mbrtowc bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The gnulib unit tests are declaring that cygwin's mbrtowc is broken. STC: #include #include #include int main () { if (setlocale (LC_ALL, "ja_JP.eucJP") != NULL) { char input[] = "B\217\253\344\217\251\316er"; mbstate_t state;

Re: gcc-3 problem when compiling

Hello Dave, [...] btw: all other bins (ar.exe, etc) in this bin directory are set to 550 That's also wrong. It should be 750. [...] Sounds to me like your real problem is that all your permissions have been trashed somehow, or whatever caused that. I can imagine that last time you ran setup

Re: volinfo (was: MVFS results)

Eric Blake wrote: > > Oh - that's why I didn't find it - csih renamed it to getVolInfo, and it > is not > part of the default PATH. > Very nice... and I found that I can mount my views on cygwin the 'standard' way! info> mkdir /view info> mount //view/emagiro_86 /view/emagiro_86 mount: warnin

Re: sh.exe: TP_NUM_W_BUFS too small?

Magnus Holmgren wrote: > When running configure scripts, I sometimes see this error message repeated > several times, for different lines of the configure script: > > bin\sh.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. > > I saw this when building libsdl 1.2.13 on Cygwin 1.7 (u

sh.exe: TP_NUM_W_BUFS too small?

When running configure scripts, I sometimes see this error message repeated several times, for different lines of the configure script: bin\sh.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. I saw this when building libsdl 1.2.13 on Cygwin 1.7 (uname -v reports 2009-07-13 10:28) o

Midnight Commander - show/hide panel

Hi All, I have been trying out Midnight Commander on Cygwin and noticed that (like vim) it has a shortcut (control+0) for going back to the command prompt. However, on Cygwin, typing anything immediately brings back Midnight Commander. I tried this on a Linux machine and it works ok, meaning I ca

Re: [1.7] Python and Unicode filenames

On Jul 20 03:02, Edward Lam wrote: > Does anyone know of the status for Unicode filename support in the cygwin > 1.7 version of Python? The last mail I found was: > > Corinna Vinschen wrote: > "Uh, so python needs a rebuild for Cygwin to deal with localized > pathnames correctly. I assume it's mi

Re: Incorrect codepage numbers in 1.7 guide

On Jul 19 21:28, Andy Koppe wrote: > A couple of small mistakes in > http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html#setup-locale-charsetlist: > ISO-8859-13 and -15 have codepage numbers 28603 and 28605, not 28563 > and 28565. Fixed. Thanks, Corinna -- Corinna Vinschen P

[1.7] Python and Unicode filenames

Does anyone know of the status for Unicode filename support in the cygwin 1.7 version of Python? The last mail I found was: Corinna Vinschen wrote: "Uh, so python needs a rebuild for Cygwin to deal with localized pathnames correctly. I assume it's missing to call the conversion functions because