Hi all,
I recently ran into a tricky problem when working with cysignals [1]
on Cygwin: Cysignals provides signal handlers for code written in C
or Cython running in a Python interpreter, which converts otherwise
unhandled signals into Python exceptions.
It recently started using sigaltstack [2]
Hi folks,
Just a little spam for a project I put together that might be of
interest to some people in the Cygwin community. Python bindings for
Cygwin's C API [1]: https://github.com/embray/PyCygwin
The first release (0.1) is pretty threadbare and does not support most
of the API yet, but I rush
On Tue, Feb 6, 2018 at 7:07 PM, Achim Gratz wrote:
> Erik Bray writes:
>> Assuming this looks good (feedback welcome) it might be nice to have
>> this patch included in the next release of the official OpenBLAS
>> package for Cygwin since its incompatibility with fork() has
Hi, Sorry for the non-response. Been traveling for the last week and
not really checking this e-mail much.
On Tue, Feb 6, 2018 at 3:15 PM, Marco Atzeri wrote:
> On 06/02/2018 13:10, Erik Bray wrote:
>>
>> Hello,
>>
>> Users/maintainers of OpenBLAS on Cygwin may be int
Hello,
Users/maintainers of OpenBLAS on Cygwin may be interested in this
patch to improve support for fork():
https://github.com/xianyi/OpenBLAS/pull/1450
Assuming this looks good (feedback welcome) it might be nice to have
this patch included in the next release of the official OpenBLAS
package
Hi all,
I've seen some reports, and encountered some problems myself, with the
new "Windows Defender Exploit Guard" [1] w.r.t. Cygwin. This enables
a number of anti-exploit protections, at least some of which might be
a problem for Cygwin--in particular "Force randomization for images
(Mandatory
Hi,
I encountered this bug through a hang in Twisted, but narrowed it down
to a simple example (in Python here, but the same would work in C).
Basically, in Twisted's system process runner, there's a "hack" [1]
which basically assumes readability (as in a poll() loop) of the
writable end of a pip
On Nov 3, 2017 9:36 PM, "Corinna Vinschen" wrote:
Hi Erik,
why didn't you send this to cygwin-patches? Not much of a problem,
just wondering...
Will follow up more later, but just to clarify on this a bit I thought the
issue was just interesting, and that the question(s) of the upper limit of
On Fri, Nov 3, 2017 at 3:45 PM, Vadim Zeitlin wrote:
> Hello,
>
> Our build has started on AppVeyor, a continuous integration provider,
> started failing since a couple of days as a makefile command running a
> Python script started failing with exit code 127 without any more
> information. This
Hi all,
I found a few bugs in Cygwin w.r.t. creating large numbers of sockets.
For example, Cygwin will gladly let you create up to RLIMIT_NOFILE
sockets (examples in Python, where I found this problem):
>>> import resource
>>> import socket
>>> resource.getrlimit(resource.RLIMIT_NOFILE)
(256, 32
On Wed, Nov 1, 2017 at 3:50 PM, Nellis, Kenneth wrote:
> Since migrating from a Windows 7 laptop to one with Windows
> 10, I've noticed a significant speed decrease in opening a
> mintty/bash window from about 0.5s to 3.5s.
>
> I've narrowed it down to two bottlenecks in .bash_profile:
> to "cygpat
On Wed, Aug 23, 2017 at 6:08 PM, Corinna Vinschen wrote:
> On Aug 23 10:33, Corinna Vinschen wrote:
>> On Aug 22 18:49, Erik Bray wrote:
>> > Hi folks,
>> >
>> > I noticed a strange discrepancy when running Cygwin through mintty, vs
>> > through a nor
Hi folks,
I noticed a strange discrepancy when running Cygwin through mintty, vs
through a normal cmd.exe console. This is on a build from the latest
git master, but also on Cygwin 2.8.0. When run from a cmd.exe
console, we can see the following output from fhandler_dev::readdir:
$ ls -l /dev/c
On Mon, Jul 17, 2017 at 11:05 AM, Corinna Vinschen wrote:
> On Jul 17 10:35, Corinna Vinschen wrote:
>> On Jul 16 19:16, Denis Excoffier wrote:
>> > Hello,
>> >
>> > I have a Cygwin installation under Windows 7 (32 bits).
>> >
>> > After 'rebase-trigger full' and 'Setup', autorebase seems to finish
On Tue, Jun 6, 2017 at 9:22 PM, Corinna Vinschen wrote:
> On Jun 6 17:57, Corinna Vinschen wrote:
>> > > On Wed, May 10, 2017 at 11:30:46AM +0200, Erik Bray wrote:
>> > >> [...]
>> > >> The attached test demonstrates the bug. Given an output buff
On Wed, May 24, 2017 at 6:57 PM, Eric Blake wrote:
> On 05/24/2017 11:53 AM, Erik Bray wrote:
>
>>>> dropping down to assembly; it could very well be that the assembly code
>>>> is incorrectly truncating things at 32 bits (where it is just fine for
>>&g
On Wed, May 24, 2017 at 5:55 PM, Erik Bray wrote:
> On Wed, May 24, 2017 at 2:33 PM, Eric Blake wrote:
>> On 05/24/2017 07:00 AM, Carl Fredrik Forsberg wrote:
>>> I am experiencing problems printing long int values under cygwin64
>>> installed on a Windows 10 machi
On Wed, May 24, 2017 at 2:33 PM, Eric Blake wrote:
> On 05/24/2017 07:00 AM, Carl Fredrik Forsberg wrote:
>> I am experiencing problems printing long int values under cygwin64 installed
>> on a Windows 10 machine.
>>
>> Below is a test program followed by its output to demonstrate the problem.
>>
On Wed, May 24, 2017 at 10:30 AM, Václav Haisman wrote:
> Hi.
>
> I have recently hit an issue ([1]) with Python 2.7 and regex package
> for it on Cygwin. It appears that Cygwin's Python 2.7 is so called
> narrow build. This causes issues when working with Unicode code point
> outside BMP, like the
On Wed, May 24, 2017 at 9:52 AM, Ronald Fischer wrote:
> I have a file X which contains ASCII text, but also in some lines German
> umlaut characters. The file is classified as:
>
> $ file X
> X: ISO-8859 text, with CRLF line terminators
>
> If I grep the file using, say,
>
> $ grep
On Sun, May 21, 2017 at 6:23 AM, Duncan Roe wrote:
> On Wed, May 10, 2017 at 11:30:46AM +0200, Erik Bray wrote:
>> Greetings--
>>
>> In the process of fixing the Python test suite on Cygwin I ran across
>> one test that was consistently causing segfaults later on, no
Greetings--
In the process of fixing the Python test suite on Cygwin I ran across
one test that was consistently causing segfaults later on, not
directly local to that test. The test involves wcsxfrm so that's
where I focused my attention.
The attached test demonstrates the bug. Given an output
On Wed, Jan 11, 2017 at 9:41 AM, Marco Atzeri wrote:
> To: cygwin-annou...@cygwin.com
> Subject: Updated: lapack-3.7.0-1
>
> New versions lapack-3.7.0-1 of
>
> lapack (source)
> liblapack0
> liblapack-devel
> liblapack-doc
>
> are available in the Cygwin distribution, 32 and 64 bit :
>
> CHANGES
>
On Mon, Apr 17, 2017 at 12:01 PM, Kptain wrote:
> I have installed python-dev package on Cygwin.
>
> It seems to be better as now I am able to build wheels for collected
> packages: numpy
>
> $ pip3 install numpy
> Collecting numpy
> Using cached numpy-1.12.1.zip
> Building wheels for collected pa
On Sat, Mar 11, 2017 at 2:29 AM, Takashi Yano wrote:
> Hello,
>
> On Fri, 10 Mar 2017 21:10:36 +0100 Corinna Vinschen wrote:
>> Thanks for the report and especially the testcase.
>>
>> It was a tricky problem to debug so it took me a while, but I think
>> I got it now.
>>
>> I uploaded new develope
On Mon, Feb 20, 2017 at 11:54 PM, Mark Geisert wrote:
> Erik Bray wrote:
>>
>> On Mon, Feb 20, 2017 at 11:54 AM, Mark Geisert wrote:
>>>>
>>>> So my guess was that Cygwin might try to hold on to a handle to a
>>>> child process at least until it&
On Mon, Feb 20, 2017 at 11:54 AM, Mark Geisert wrote:
>> So my guess was that Cygwin might try to hold on to a handle to a
>> child process at least until it's been explicitly wait()ed. But that
>> does not seem to be the case after all.
>
>
> You might have missed a subtlety in what I said above.
On Fri, Feb 17, 2017 at 11:06 PM, Mark Geisert wrote:
> Erik Bray wrote:
>>
>> On Tue, Feb 14, 2017 at 8:25 PM, Mark Geisert wrote:
>
>
> Please don't quote raw email addresses. We try to avoid feeding spammers.
Sorry--normally replies on this ML are just back to
On Tue, Feb 14, 2017 at 8:25 PM, Mark Geisert wrote:
> Erik Bray wrote:
>>
>> The attached Python script
>
>
> ??
D'oh! Here is the script. It at least demonstrates the problem.
test.py
Description: Binary data
--
Problem reports: http:/
Hi all,
I encountered a strange bug concerning zombie child processes during
my testing. Specifically, it came up in the context of trying to read
the /proc/ entries of processes that should be zombified but not
reaped yet (i.e. they have received and processed a SIGKILL or SIGTERM
but have not b
On Thu, Feb 2, 2017 at 2:08 PM, Corinna Vinschen
wrote:
> On Feb 2 12:19, Erik Bray wrote:
>> Hi all,
>>
>> I've been trying to get a Cygwin sshd server running on a Windows 10
>> VM, and have found it to be surprisingly tricky without some
>> additio
Hi all,
I've been trying to get a Cygwin sshd server running on a Windows 10
VM, and have found it to be surprisingly tricky without some
additional fiddling, and it's not clear to me whether that's expected
or if it's a bug. I've attached the cygcheck output from the VM.
The symptom I've having
On Mon, Jan 9, 2017 at 6:16 PM, Corinna Vinschen
wrote:
> On Jan 9 16:46, Erik Bray wrote:
>> Hi Corinna,
>>
>> Thanks for the response.
>>
>> On Mon, Jan 9, 2017 at 3:13 PM, Corinna Vinschen wrote:
>> > Right. It has to do with how connect/accept wor
Hi Corinna,
Thanks for the response.
On Mon, Jan 9, 2017 at 3:13 PM, Corinna Vinschen
wrote:
> Hi Erik,
>
> On Jan 9 14:29, Erik Bray wrote:
>> On Mon, Jan 9, 2017 at 12:01 PM, Erik Bray wrote:
>> > On Fri, Jan 6, 2017 at 12:40 PM, Erik Bray wrote:
>> &g
On Mon, Jan 9, 2017 at 12:01 PM, Erik Bray wrote:
> On Fri, Jan 6, 2017 at 12:40 PM, Erik Bray wrote:
>> Hello, and happy new-ish year,
>>
>> I've been working on and off over the past few months on bringing
>> Python's compatibility with Cygwin up to snu
On Fri, Jan 6, 2017 at 12:40 PM, Erik Bray wrote:
> Hello, and happy new-ish year,
>
> I've been working on and off over the past few months on bringing
> Python's compatibility with Cygwin up to snuff, including having all
> pertinent tests passing. I've notice
Hello, and happy new-ish year,
I've been working on and off over the past few months on bringing
Python's compatibility with Cygwin up to snuff, including having all
pertinent tests passing. I've noticed that there are several tests
(which I currently skip) that cause the process to hang indefini
lso find it .
You need to make sure that cygwin1.dll and any other required DLLs are
bundled with your application, preferably in the same directory, or
else it won't be able to find them. There's a good tutorial here:
https://www.youtube.com/watch?v=abM_ysmpenc
> On 2016/12/20 0:45
On Mon, Dec 19, 2016 at 4:07 PM, Goodman Leung wrote:
> hi all
>
> i install python and pyinstaller on cygwin , and i can run pyinstaller
> successfully to compile a exe file on the cygwin environment .
>
> but when i launch this executable file on window with double click , it
> occur a error an
On Wed, Nov 30, 2016 at 11:43 AM, Corinna Vinschen
wrote:
> Hi Erik,
>
> On Nov 29 14:26, Erik Bray wrote:
>> On Thu, Nov 17, 2016 at 3:00 PM, Corinna Vinschen
>> wrote:
>> > On Nov 17 14:30, Erik Bray wrote:
>> >> Hi all,
>> >>
>>
On Wed, Nov 30, 2016 at 10:15 AM, Peter Rosin wrote:
> On 2016-11-30 04:00, Eliot Moss wrote:
>> On 11/29/2016 7:28 PM, Herbert Stocker wrote:
>>
>>> Or we simply copy the variables unconverted to the Windows environment
>>> block, as the Windows env block is not used for anything else - up to
>>>
On Tue, Nov 29, 2016 at 3:28 PM, Eliot Moss wrote:
> On 11/29/2016 8:26 AM, Erik Bray wrote:
>>
>> On Thu, Nov 17, 2016 at 3:00 PM, Corinna Vinschen
>> wrote:
>>>
>>> On Nov 17 14:30, Erik Bray wrote:
>>>>
>>>> Hi all,
>>>
On Thu, Nov 17, 2016 at 3:00 PM, Corinna Vinschen
wrote:
> On Nov 17 14:30, Erik Bray wrote:
>> Hi all,
>>
>> For a quick bit of background, I'm working on porting the highly
>> useful psutil [1] Python library to Cygwin. This has proved an
>> interesting
On Wed, Nov 23, 2016 at 4:24 AM, Jason Bell wrote:
> Hi -
>
> The newest version of cygwin with python 2.7.12-1 fails when pip
> installing packages that require compilation. For example, pycrypto
> fails:
>
> $ pip install pycrypto
> Collecting pycrypto
> ...
> building 'Crypto.PublicKey._
Hi all,
For a quick bit of background, I'm working on porting the highly
useful psutil [1] Python library to Cygwin. This has proved an
interesting exercise, as much of the functionality of psutil works on
Cygwin through existing POSIX interfaces, and a handful of
Linux-specific interfaces as wel
On Thu, Aug 11, 2016 at 4:13 PM, Corinna Vinschen
wrote:
> Hi Eric,
>
> On Aug 11 11:51, Erik Bray wrote:
>> [...]
>> > Existing implementations vary on the result of a kill() with pid
>> > indicating an inactive process (a
>> > terminated process
Hi all,
This is a followup to a report back in 2011 about essentially the same issue:
https://cygwin.com/ml/cygwin/2011-04/msg00031.html
The same test program in that report demonstrates the issue, but with
kill sending any non-zero signal. To reiterate, the problem here is
POSIX compliance wit
Hi all,
This issue pertains to Cygwin 64-bit. The following example program
demonstrates the issue:
$ cat mmap_test.c
#include
#include
#include
#define VSIZE 0x11000
#define SIZE 0x1000
void foo() {
void *top, *bot, *c;
c = mmap(NULL, VSIZE, PROT_READ|PROT_WRITE,
48 matches
Mail list logo
