[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.1.0-0.1

2015-06-20 Thread Corinna Vinschen
Hi Cygwin friends and users, I released a TEST version of Cygwin. The version number is 2.1.0-0.1. This test release is mostly for interested *developers*. The important news which needs some testing is the implementation of sigaltstack(2) and the underlying implementation of running a signal

Re: gdb arbitrarily starting threads

2015-06-20 Thread William M. (Mike) Miller
On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown wrote: > On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote: >> >> Thanks for the reply. My concern, however, isn't that new threads are >> being created; it's that when gdb does this, it sets the state of all >> threads, including my main thread, to "

Re: gdb arbitrarily starting threads

2015-06-20 Thread Ken Brown
On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote: Thanks for the reply. My concern, however, isn't that new threads are being created; it's that when gdb does this, it sets the state of all threads, including my main thread, to "(running)" so that I can't single-step through my program any m

Re: gdb arbitrarily starting threads

2015-06-20 Thread William M. (Mike) Miller
On Sat, Jun 20, 2015 at 2:47 PM, Corinna Vinschen wrote: > On Jun 20 09:29, William M. (Mike) Miller wrote: >> I have a single-threaded executable that has a number of debug-print >> routines that can be called interactively in the debugger to display >> data structures to stderr. Something has c

Re: gdb arbitrarily starting threads

2015-06-20 Thread Corinna Vinschen
On Jun 20 09:29, William M. (Mike) Miller wrote: > I have a single-threaded executable that has a number of debug-print > routines that can be called interactively in the debugger to display > data structures to stderr. Something has changed in gdb/gcc/Cygwin > during the last year or so (I don't

cacls combination problem in 1.7.35, merging privs of existing file & privs of process

2015-06-20 Thread John Ruckstuhl
I'm noticing this summer, that whenever I try to edit an existing file with vi for the first time, the file's permissions change. Could this be a problem with merging permissions of existing file and permissions of the vi process? Original cacls of file try2.txt: try2.txt INTSURG\johnru:(R,W

gdb arbitrarily starting threads

2015-06-20 Thread William M. (Mike) Miller
I have a single-threaded executable that has a number of debug-print routines that can be called interactively in the debugger to display data structures to stderr. Something has changed in gdb/gcc/Cygwin during the last year or so (I don't update my installation very often) so that when I call on