X-Spam-Check-By: sourceware.org Date: Mon, 7 Aug 2006 16:10:38 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: crashes with various programs Message-ID: <20060807201038.GA1279@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060807194955 DOT GA5376 AT ingber DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060807194955.GA5376@ingber.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Aug 07, 2006 at 12:49:56PM -0700, Lester Ingber wrote: >Since the latest round of updates with cygwin1.dll, I've been having >various programs crash regularly (daily, sometimes several times per day). >Lot of times my xterm windows just exit. Here is an example of a >non-X program, /usr/bin/pstree that regularly crashes: > >% pstree >Segmentation fault (core dumped) > >or > >% pstree -p -l >Exception: STATUS_ACCESS_VIOLATION at eip=610DD891 >eax=00000000 ebx=0022C3E8 ecx=FFFFFFFF edx=00000001 esi=00660AE8 edi=00000001 >ebp=0022C348 esp=0022C344 program=C:\cygwin\bin\pstree.exe, pid 5972, thread main >cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 >Stack trace: >Frame Function Args >0022C348 610DD891 (00000001, 0022C360, 00405563, 0022C3F0) >0022C3D8 610E3F24 (00000001, 0040556D, 0022C850, 000009A8) >0022CCE8 61092068 (00000003, 61169E2C, 00660090, 00000000) >0022CD98 61006168 (00000000, 0022CDD0, 610054E0, 0022CDD0) >610054E0 61004416 (0000009C, A02404C7, E8610FF1, FFFFFF48) > 22 [main] pstree 5972 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) >Segmentation fault (core dumped) That stackdump doesn't make any sense given the 1.5.21 cygwin1.dll. I don't know if that is a clue or not but maybe adding error_start=c:/cygwin/bin/gdb.exe to your CYGWIN environment variable might help see where this is actually dying. To get symbolic information you'd also have to install cygwin1.dbg from the cygwin source tar ball into /bin. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/