Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 3 May 2001 10:50:12 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: 1.3.2 ho! Message-ID: <20010503105012.A4464@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from matt@use.net on Wed, May 02, 2001 at 09:48:50PM -0700 On Wed, May 02, 2001 at 09:48:50PM -0700, Matt wrote: >On Tue, 1 May 2001, Matt wrote: > >> On Tue, 1 May 2001, Christopher Faylor wrote: >> >> > What needs to be fixed for 1.3.2? >> > >> > Here are the bugs that I am aware of: >> >> I'm noticing that on my win98 machine that ssh.exe seems to exit, but is >> still running according to the process list. When I try to exit from >> cygwin, cygwin will not exit until that ssh.exe is killed first. >> >> Let me try and reproduce with a snapshot and if the problem still exists, >> attach to the ssh process with gdb and see if I can tell what's going on. >> Regardless, I'll update the list with what I can infer. > >When I try to attach to the ssh in lala-land with GDB, gdb appears to >choke and use a lot of CPU. gdb couldn't attach using the Cygwin process >ID, so I used the Windows PID instead. GDB output a message saying it was >attaching to process -2349823 (or somesuch number). Um, yeah. GDB uses the windows pid. It always has. What version of gdb are you using? I have no problems attaching to processes. Unfortunately, the strace was useless. cgf