Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Dave Korn" To: Subject: RE: autossh crash with 20050314 and earlier cygwin1.dll Date: Wed, 16 Mar 2005 15:57:55 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 16 Mar 2005 15:57:34.0810 (UTC) FILETIME=[DE7043A0:01C52A40] ----Original Message---- >From: David Rothenberger >Sent: 16 March 2005 04:20 > Andrew. It has crashed twice in the few weeks and I've captured stack > traces for each. I was running a debugging copy of the Cygwin DLL (built > myself from CVS) in each case and I've run addr2line on each stack > trace. The second stack trace was running the DLL build from CVS at > 20050314 19:52:25 PDT. I don't have the date of the DDL for the first > stack trace, but it was an earlier one. 0065E938 61093A1F (6112B460, 7974742F, 61120031, 6974616D) malloc.cc:3952 nextchunk = chunk_at_offset(p, size); nextsize = chunksize(nextchunk); yeesh. nasty heap corruption leading to bad nextchunk pointer and an exception when it is dereferenced in the attempt to find nextsize. happening in a realloc call. ugly. it's going to be hard to track down; whatever is causing the corruption may be taking place an arbitrary amount of time prior to when the exception happens, and not necessarily in the same thread either. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/