Message-ID: <51430914.6010901@cs.utoronto.ca>
Date: Fri, 15 Mar 2013 07:42:12 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: ^C and new signal-aware snapshot
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hi all,

I found a problem (or unintended effect? or WJM feature?) with the new 
change that makes gdb work with cygwin signals:

1. start sqlite3
2. ^z
3. jobs -p
4. in separate terminal window, gdb -p $PID
5. c
6. in first window, fg
7. in gdb window, gdb should have caught SIGCONT, c
8. gdb and sqlite3 are now deadlocked (neither responds to ^c or ^z), 
you have to kill gdb to escape.

I realize that messing with SIGCONT is a good way to confuse the app, 
but (a) I didn't want to (surprise!) and (b) is there a way to make the 
penalty for forgetting to ignore SIGCONT a little less draconian?

Thanks,
Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple