Re: malloc(0) crashing with SIGABRT

On 2019-09-11 20:59, Brian Inglis wrote: On 2019-09-09 11:13, Petr Skočík wrote: There's been a twitter discussion on how different POSIX platforms handle malloc(0): https://twitter.com/sortiecat/status/1170697927804817412 . As for Cygwin, the answer appears to be "not well", but this should

Re: Where is igawk and why doesn't @include replicate this feature?

On 2019-09-11 05:52, Steven Penny wrote: > On Wed, 11 Sep 2019 16:54:49, Troy Kenah wrote: >> I used to embed @include junk.awk statements to reduce repetitive code but >> this no longer works. These were files were not functions, simply code >> snippets; this is the type of error I am now seeing:

Re: malloc(0) crashing with SIGABRT

On 2019-09-09 11:13, Petr Skočík wrote: > There's been a twitter discussion on how different POSIX platforms > handle malloc(0): https://twitter.com/sortiecat/status/1170697927804817412 . > > As for Cygwin, the answer appears to be "not well", but this should be > easy to fix. POSIX SUS V4 2018 s

Re: retry: Problem transfering X11 cut/copy buffer to windows and back

I sometimes get in this situation where one and only one xterm receives a paste no matter which window (X or Windows) I'm trying to paste into. THIS IS NOT A BUG REPORT, my cygwin is pretty old. However I've found oddly enough if I go into the xterm receiving all the pastes and press CTRL-mouse

Re: Where is igawk and why doesn't @include replicate this feature?

On 2019-09-10 23:54, Troy Kenah wrote: Hi All, I have a large number of scripts that were using the the igawk script, however I have updated my gawk to a newer release that has obsoleted/removed the igawk script. Gawk's build system stopped installing igawk over five years ago: http://git.sav

Re: retry: Problem transfering X11 cut/copy buffer to windows and back

On Wed, Sep 11, 2019 at 8:52 AM Jon Turney wrote: > > 1. Is there any information I can provide to help debug this problem? > > A reliable way of reproducing the problem would be ideal :) I wish! > Failing that, the /var/log/xwin/XWin.0.log might be informative. > > > 2. Is there a way to rese

Re: XTerm(331)?

Thanks everyone, and Yaakov, for releasing (348). -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsub

[ANNOUNCEMENT] tzcode/tzdata 2019c-1

The following packages have been uploaded to the Cygwin distribution: * tzcode-2019c-1 * tzdata-2019c-1 The Time Zone Database (often called tz or zoneinfo) contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodic

[ANNOUNCEMENT] xterm 348-1

The following packages have been uploaded to the Cygwin distribution: * xterm-348-1 The xterm program is a terminal emulator for the X Window System. It provides DEC VT102 and Tektronix 4014 compatible terminals for programs that can't use the window system directly. This version implements ISO

Re: XTerm(331)?

- Original Message - | From: "Jim Reisert AD1C" | To: "cygwin" | Sent: Wednesday, September 11, 2019 10:26:56 AM | Subject: XTerm(331)? | Can someone please update the Cygwin XTerm? The current version is | (330) but I understand (331) is out there, at least in Fedora: | | [JJR:~] $ xt

Re: printf, "unable to initialize PRN" message

Am 11.09.2019 um 02:03 schrieb Blair, Charles E III: > I have just installed cygwin (64 bit) and gcc. The "hello world" program > works, but > > #include > int main(){printf( "%c\n" , 'X' );return 0;} > > leads to > > Unable to initialize device PRN > Unable to initialize device PRN I suspec

Re: XTerm(331)?

Am 11.09.2019 um 16:26 schrieb Jim Reisert AD1C: Can someone please update the Cygwin XTerm? The current version is (330) but I understand (331) is out there, at least in Fedora: [JJR:~] $ xterm -version XTerm(330) https://bugzilla.redhat.com/show_bug.cgi?id=1534475 "xterm-331-1.fc27 has been

Re: Where is igawk and why doesn't @include replicate this feature?

Troy Kenah writes: > I have a large number of scripts that were using the the igawk script, > however I have updated my gawk to a newer release that has > obsoleted/removed the igawk script. The semantics for @include are different between igawk and "native" gawk @include (since 4.x). The newer g

Re: retry: Problem transfering X11 cut/copy buffer to windows and back

On 11/09/2019 00:17, Jim Reisert AD1C wrote: I didn't see this message before I posted a separate message. Here is my report again. I am using the latest test X server (1.20.5-3 built 2019-09-06), HOWEVER, I have seen this problem again and again for months now. After I copy/paste enough, eith

Re: Fwd: Report

>1 [main] cntlm 14392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD=20 >pointer. Please report this problem to >the public mailing list cygwin@cygwin.com >cygwin warning: > MS-DOS style path detected: C:\Program Files (x86)\Cntlm\cntlm.ini > Preferred POSIX equivalent is: /Cntlm/cntlm.in

Fwd: Report

1 [main] cntlm 14392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com cygwin warning: MS-DOS style path detected: C:\Program Files (x86)\Cntlm\cntlm.ini Preferred POSIX equivalent is: /Cntlm/cntlm.ini CYGWI

XTerm(331)?

Can someone please update the Cygwin XTerm? The current version is (330) but I understand (331) is out there, at least in Fedora: [JJR:~] $ xterm -version XTerm(330) https://bugzilla.redhat.com/show_bug.cgi?id=1534475 "xterm-331-1.fc27 has been pushed to the Fedora 27 stable repository. If prob

Re: Where is igawk and why doesn't @include replicate this feature?

On Wed, 11 Sep 2019 16:54:49, Troy Kenah wrote: I used to embed @include junk.awk statements to reduce repetitive code but this no longer works. These were files were not functions, simply code snippets; this is the type of error I am now seeing: gawk: get_FY2019Q1OIC.awk:28: @include "../inc/se