20110117 snapshot crashes with rxvt and tcsh

I am having tcsh "out of memory" problems when running tcsh under rxvt with the latest snapshot (20110127). I do not see the failure if I am not running under rxvt. I also do not see the problem if I repeatedly run bash shells. This problem also existed with the 20101201 snaps

[ANNOUNCEMENT] Updated: {libiconv/libiconv2/libcharset1}-1.13.1-2

The GNU libiconv package provides an iconv() implementation, for use on systems which don't have one, or whose implementation cannot convert from/to Unicode. [[ compiled using gcc-4.3.4-3 ]] Changes since libiconv-1.13.1-1 o Rebuild against newer cygwin [*

Re: vim wraps lines

On Thu, 27 Jan 2011 17:22:41 -0500, Larry Hall (Cygwin) wrote: I notice you're behind one step on the cygwin package. I don't think that's a contributor but you should update. I updated and the problem went away. thanks Daniel -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: [ANNOUNCEMENT] Updated: cygport-0.10.3

On 1/27/2011 12:06 PM, Yaakov (Cygwin/X) wrote: > On Thu, 2011-01-27 at 11:04 -0500, Charles Wilson wrote: >> On 1/26/2011 8:10 PM, Yaakov (Cygwin/X) wrote: >>> I have updated the cygport to version 0.10.3 with the following changes: >> >>> * Fixed default excludes where libtool is used without aut

Re: vim wraps lines

On 1/27/2011 1:25 PM, Daniel Ajoy wrote: On Thu, 27 Jan 2011 00:44:34 -0500, Daniel Ajoy wrote: ^^^ On Wed, 26 Jan 2011 22:12:01 -0500, Larry Hall (Cygwin) <> wrote: ^

Re: cygwin patches for gnulib relocation code [Was: Re: Bug in libiconv?]

On 1/27/2011 3:12 PM, Eric Blake wrote: > On 01/27/2011 11:35 AM, Charles Wilson wrote: >> Eric (Blake), you're active on the gnulib list. Care to comment? > > Answering with my gnulib maintainer hat on (and yes, I am one of the > core gnulib maintainers) - Bruno Haible likes to keep cygwin 1.5 >

Re: libglade error during cygwin installation

On Thu, Jan 27, 2011 at 06:41:18PM +, Joe Crepeau wrote: > I am getting the following error when installing the latest version of Cygwin > on a Windows 7 machine. > > 2011/01/21 16:02:23 running: C:\cygwin\bin\bash.exe --norc --noprofile > /etc/postinstall/libglade2.0.sh > add command failed

Re: cygwin patches for gnulib relocation code [Was: Re: Bug in libiconv?]

On 01/27/2011 11:35 AM, Charles Wilson wrote: > On 1/27/2011 12:08 PM, Corinna Vinschen wrote: >> Cygwin Versions prior to 1.7.7 are not support anyway. > > This is merely semantics. You're saying that *the cygwin project* does > not support older cygwins. However, that doesn't mean *other projec

pthread_cancel+pthread_join problems when a thread executes "accept" TCP function

I have detected an issue with pthread_join when the thread is executing "accept" TCP function. If a thread is blocked in an accept TCP call, and a "pthread_cancel" and "pthread_join" are called from parent, in cygwin, the "pthread_join" is blocked forever until "accept" ends (that maybe never end)

Re: max memory

On Mon, 24 Jan 2011, Christopher Faylor wrote: > On Sun, Jan 23, 2011 at 08:11:52PM -0800, Linda Walsh wrote: > >Christopher Faylor wrote: > >> Cygwin only uses as much memory as the OS gives it. It can't > >> use a full 2048MB for the heap. > > > > > >Using the /LARGEADDRESSAWARE flag would

libglade error during cygwin installation

I am getting the following error when installing the latest version of Cygwin on a Windows 7 machine. Package: Unknown package     libglade2.0.sh exit code 3 Below is the tail end of the /var/log/setup.log.full file. 2011/01/21 16:02:02 running: C:\cygwin\bin\bash.exe --norc --noprofile

cygwin patches for gnulib relocation code [Was: Re: Bug in libiconv?]

On 1/27/2011 12:08 PM, Corinna Vinschen wrote: > Cygwin Versions prior to 1.7.7 are not support anyway. This is merely semantics. You're saying that *the cygwin project* does not support older cygwins. However, that doesn't mean *other projects* have the same policy -- see, for instance, upstream

Re: vim wraps lines

On Thu, 27 Jan 2011 00:44:34 -0500, Daniel Ajoy wrote: On Wed, 26 Jan 2011 22:12:01 -0500, Larry Hall (Cygwin) wrote: I can't reproduce that behavior. What's your TERM environment variable set to? echo $TERM xterm It's most likely a problem with the TERM setting in use when vim was s

Re: Tcl file separator

On 1/27/2011 12:18 PM, Yaakov (Cygwin/X) wrote: > On Wed, 2011-01-26 at 00:33 -0500, Christopher Faylor wrote: >> I'm working on this very very slowly but I don't have an ETA for when this >> will >> be fixed. > > What exactly are you trying to "fix"? I thought we agreed that the > solution was

[ANNOUNCEMENT] Updated: OpenSSH-5.7p1-1

I've just updated the Cygwin version of OpenSSH to 5.7p1-1. This is a new major upstream release. The Cygwin release is created from the vanilla sources. The official release message of 5.7p1: OpenSSH 5.7 has just been release

Re: [1.7.7 +] startxwin works unless using recent cygwin1.dll snapshot

; > However I did find that when using the snapshot DLL, "startxwin" fails. > > When using the original 1.7.7 DLL, X runs fine. I also tried the new > > 20110127 snapshot and it didn't help startxwin. I did try rebaseall for no > > particular reason but it did

Re: [1.7.7 +] startxwin works unless using recent cygwin1.dll snapshot

ort memory and give us pointers to these threads? > reproducible enough to diagnose, so that is not the subject of this > message. > > However I did find that when using the snapshot DLL, "startxwin" fails. > When using the original 1.7.7 DLL, X runs fine. I also tried th

Re: Tcl file separator

On Wed, 2011-01-26 at 00:33 -0500, Christopher Faylor wrote: > Tcl is currently one part of the Cygwin installation that is pretty much > pure windows. It is that way for the sole purpose of working with the > insight debugger. So it takes windows paths and is not a real Cygwin > application. >

Re: Bug in libiconv?

On Jan 27 11:21, Charles Wilson wrote: > On 1/27/2011 7:20 AM, Corinna Vinschen wrote: > > I got it working. The major reason was that the conversion to wchar_t > > was broken due to the #if expressions in lib/iconv.c and > > lib/iconv_open1.h: > > > > #if __STDC_ISO_10646__ || ((defined _WIN32

Re: [ANNOUNCEMENT] Updated: cygport-0.10.3

On Thu, 2011-01-27 at 11:04 -0500, Charles Wilson wrote: > On 1/26/2011 8:10 PM, Yaakov (Cygwin/X) wrote: > > I have updated the cygport to version 0.10.3 with the following changes: > > > * Fixed default excludes where libtool is used without automake. > > Are you sure about this? I ran into th

Re: Bug in libiconv?

On 1/27/2011 7:20 AM, Corinna Vinschen wrote: > I got it working. The major reason was that the conversion to wchar_t > was broken due to the #if expressions in lib/iconv.c and > lib/iconv_open1.h: > > #if __STDC_ISO_10646__ || ((defined _WIN32 || defined __WIN32__) && > !defined __CYGWIN__) >

Re: Bug in libiconv?

On 1/27/2011 4:25 AM, Corinna Vinschen wrote: > On Jan 26 22:12, Charles Wilson wrote: >> Can we get a newer snapshot that the current 20110117? > > Done. Thanks. Will try again (with today's snap #2) tonight. -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: [ANNOUNCEMENT] Updated: cygport-0.10.3

On 1/26/2011 8:10 PM, Yaakov (Cygwin/X) wrote: > I have updated the cygport to version 0.10.3 with the following changes: > * Fixed default excludes where libtool is used without automake. Are you sure about this? I ran into this problem with libiconv + cygport-0.10.2, so I updated to 0.10.3, bu

RE: Tcl file separator

From: Christopher Faylor > Tcl is currently one part of the Cygwin installation that is pretty > much pure windows. It is that way for the sole purpose of working > with the insight debugger. So it takes windows paths and is not a > real Cygwin application. > > I'm working on this very very slow

Re: Bug in libiconv?

On Jan 26 22:09, Charles Wilson wrote: > On 1/24/2011 10:09 PM, Charles Wilson wrote: > > Now, since there has not yet been an updated upstream release of > > libiconv, my first step would be to simply rebuild our existing > > libiconv-1.13.1 on a platform with current cygwin (1.7.7-1), and try the

Re: Bug in libiconv?

> If that doesn't correct the issue...then I'd try to run your test case > on linux, but *explicitly* using libiconv on that system, rather than > (as is typically the case on linux) relying on the underlying glibc > implementation of iconv functionality. > > Did this. Here are the characteristics

Re: Bug in libiconv?

On Jan 26 22:12, Charles Wilson wrote: > On 1/25/2011 6:15 AM, Corinna Vinschen wrote: > > - lib/iconv_open1.h and lib/iconv.c exclude Cygwin from the usage of the > > ei_ucs2internal encoding table. I'm not sure if that's right or > > wrong, but it looks worrying. Please note that I defined

Re: Still on target for imminent 1.7.8 release? [was Re: Enable dfp routines in compiler support lib]

On Jan 26 17:05, Yaakov (Cygwin/X) wrote: > On Wed, 2011-01-26 at 11:33 +0100, Corinna Vinschen wrote: > > On Jan 26 03:53, Dave Korn wrote: > > > Hey, main list! Are we still expecting 1.7.8 by the end of this month? > > > > Early Feb is more likely. From my POV there's just that new issue wi