Re: Cygwin multithreading performance

Corinna Vinschen wrote: On Nov 21 01:21, Mark Geisert wrote: [...] so I wonder if there's some unintentional serialization going on somewhere, but I don't know yet how I could verify that theory. If I'm allowed to make an educated guess, the big serializer in Cygwin are probably the calls to

Re: Octave 4.0.0-3 x86_64 segfault (suspect openblas)

On 23/11/2015 04:33, Tony Kelman wrote: The following works fine on 32 bit, but segfaults reliably on 64 bit: $ octave [cut] octave:1> D = 1000*(rand(1000,1000)-0.5); octave:2> [E,F] = eig(D) panic: Segmentation fault -- stopping myself... attempting to save variables to 'octave-workspace'...

Re: startx doesn't seem to work

On 22/11/2015 04:18, Peter Van Epp wrote: On my Win7 machine with a newly installed cygwin-64 installed via setup-x86_64.exe with everything default except xinit and xorg-server selected running startx from a terminal window opens a full screen window and then dies. A search of startx fai

Git issue.

I've run into a problem when using the --git-dir option in git. It appears to have been introduced since git 2.4.x. Here's an example of the problem using a locally built version (2.6.3) of git with some annotated error output: [/cygdrive/d/projects] $ git --version git version 2.6.3-cyg [/cyg

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

Thanks for giving it a look. On 11/22/15, Ken Brown wrote: > On 11/21/2015 7:48 PM, David Standish wrote: >> Ken, I'm not surprised it works for you. Probably something with my >> machine. >> >> I've attached cygcheck -s -v -r output > > Sorry, nothing jumps out at me. Maybe someone else will

Re: cygwin 64bit on Win7 gcc internal compiler error: Segmentation fault on floating point literal 10.0

On 11/21/2015 7:48 PM, David Standish wrote: Ken, I'm not surprised it works for you. Probably something with my machine. I've attached cygcheck -s -v -r output Sorry, nothing jumps out at me. Maybe someone else will have some ideas. Ken -- Problem reports: http://cygwin.com/problems

Re: Windows locks up when pressing Ctrl+S while native process writes to terminal

Hello, I found a consistent bug that happens every time: ... - Press Ctrl+S to stop the output in the terminal Bug #1: It's not possible to unfreeze the output in the terminal with Ctrl+Q. It just stays "stuck" I confirm this effect and you don't need a fat application to demonstrate it. Wit

Re: Errors in handling of boost::asio errors ('boost' was compiled with wrong std::string representation?)

Роман wrote at 11:33 +0600 on Nov 21, 2015: > Following program: > > --- begin of code > #include > #include > > int main() > { > std::string s = > boost::system::generic_category().message(22); > > printf("size=%lu, c_str=\"%s\".\n", > s.size()