Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 25 Jan 2001 11:30:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: OpenSSH crashes - able to repeat the cause Message-ID: <20010125113051.C30263@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010125111430 DOT B30263 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010125111430.B30263@redhat.com>; from cgf@redhat.com on Thu, Jan 25, 2001 at 11:14:30AM -0500 On Thu, Jan 25, 2001 at 11:14:30AM -0500, Christopher Faylor wrote: >On Thu, Jan 25, 2001 at 10:46:19AM -0500, Jack Radigan wrote: >>I'm doing the same at the moment. When id.exe crashes go over to the >>system and do a 'ps' to find out the pid of id.exe. Then, start gdb with: >> >> gdb program >> >>I'm able to see the registers but the stack is lost in space somewhere >>and doesn't show anything relevant. > >Switch to the main thread (probably thread 1). Also configure cygwin with "--enable-debugging" and you can set the CYGWIN_SLEEP environment variable to some number of milliseconds (like 10000). This will cause every cygwin application to wait for that number of milliseconds, printing its pid. You can then attach gdb to the pid. You'll have to set CYGWIN_SLEEP as a global environment variable. Setting it in .profile or .bashrc probably won't work. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple