Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 13 Oct 2002 22:32:23 -0500
From: Steve O <bub AT io DOT com>
To: cygwin AT cygwin DOT com
Subject: latest cvs fork problems
Message-ID: <20021013223223.D10723@eris.io.com>
References: <200210140309 DOT WAA25780 AT deliverator DOT io DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200210140309.WAA25780@deliverator.io.com>; from MAILER-DAEMON@sources.redhat.com on Mon, Oct 14, 2002 at 03:09:50AM -0000

On Mon, Oct 14, 2002 at 03:09:50AM -0000, MAILER-DAEMON AT sources DOT redhat DOT com wrote:
> <cygwin-developers AT cygwin DOT com>:
> Sorry, only subscribers may post.  See the project web page for details: http://www.cygwin.com/lists.html (#5.7.2)

Hi,
I was trying to get the latest cygwin CVS working and ran into some 
difficulties.  An strace of rxvt hangs as it forks:

...
   36  135315 [main] rxvt 1644 void: 0x0 = signal (3, 0x4010B8)
   36  135351 [main] rxvt 1644 void: 0x0 = signal (15, 0x4010B8)
   36  135387 [main] rxvt 1644 void: 0x0 = signal (20, 0x401048)
   43  135430 [main] rxvt 1644 fork: entering
  468  135898 [proc] rxvt 1644 wait_subproc: starting


hitting Control-C hangs here:

...
   51 5778824 [unknown (0xAA8)] rxvt 1644 kill_worker: 0 = kill_worker (1644, 2)
   37 5778861 [unknown (0xAA8)] rxvt 1644 kill_pgrp: 0 = kill (1644, 2)
  343 5779204 [sig] rxvt 1644 wait_sig: looping

hitting another Control-C starts a loop:

1921941 7701145 [unknown (0x338)] rxvt 1644 _kill: kill (-1644, 2)
  132 7701277 [unknown (0x338)] rxvt 1644 kill_pgrp: pid 1644, signal 2
 1046 7702323 [unknown (0x338)] rxvt 1644 kill_pgrp: killing pid 1644, pgrp 1644, p->ctty 1073741824, myself->ctty 1073741824
   82 7702405 [unknown (0x338)] rxvt 1644 sig_send: pid 1644, signal 2, its_me 1
   44 7702449 [unknown (0x338)] rxvt 1644 sig_send: Waiting for thiscomplete 0x758
 1280 7703729 [sig] rxvt 1644 wait_sig: awake
  121 7703850 [sig] rxvt 1644 wait_sig: processing signal 2
   42 7703892 [sig] rxvt 1644 wait_sig: Got signal 2
   41 7703933 [sig] rxvt 1644 sig_handle: signal 2
   42 7703975 [sig] rxvt 1644 sig_handle: signal 2, about to call 0x4010B8
   53 7704028 [sig] rxvt 1644 setup_handler: couldn't send signal 2
   42 7704070 [sig] rxvt 1644 setup_handler: good.  Didn't suspend main thread, th 0x0
   40 7704110 [sig] rxvt 1644 setup_handler: returning 0
   39 7704149 [sig] rxvt 1644 sig_handle: returning 0
   51 7704200 [unknown (0x338)] rxvt 1644 sig_send: returning 0 from sending signal 2
   50 7704250 [unknown (0x338)] rxvt 1644 kill_worker: 0 = kill_worker (1644, 2)
   38 7704288 [unknown (0x338)] rxvt 1644 kill_pgrp: 0 = kill (1644, 2)
  302 7704590 [sig] rxvt 1644 wait_sig: looping
   60 7704650 [sig] rxvt 1644 wait_sig: awake
   ...


The edit that creates this behavior is:
http://cygwin.com/ml/cygwin-cvs/2002-q4/msg00022.html

cvs up -A
cvs up -D '2002-10-08 22:50:00' cygthread.cc cygthread.h fhandler.h fhandler_tty.cc sigproc.cc tty.cc

gets me a working cygwin.

Thanks.
-steve

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/