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 To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: RE: autossh crash with 20050314 and earlier cygwin1.dll Date: Wed, 16 Mar 2005 12:07:53 -0500 Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: pcp04399769pcs.nrockv01.md.comcast.net User-Agent: MicroPlanet-Gravity/2.70.2067 X-Archive: encrypt X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner-SpamScore: s X-MailScanner-From: goc-cygwin AT m DOT gmane DOT org X-MailScanner-To: cygwin AT cygwin DOT com X-IsSubscribed: yes > 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. Would the job be easier in my case, where I have a repeatable crash? I provided strace output in the earlier thread about my autossh problems, but haven't tried using any debug builds of cygwin1.dll. I'm not conversant with debuggers, but I have used gdb before and could work my way through it. Let me know if this would be useful, and how best to go about it. Of course there's no guarantee that my crash and David's have the same cause, but they might well and it would be as good a place as any to start. -- 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/