| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-Spam-Check-By: | sourceware.org |
| Date: | Thu, 4 Nov 2010 15:43:15 -0400 |
| From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: 1.7.7: sh.exe sometimes hangs with 100% cpu usage |
| Message-ID: | <20101104194314.GA13448@ednor.casa.cgf.cx> |
| Reply-To: | cygwin AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <1906373454 DOT 1857461288894772454 DOT JavaMail DOT root AT spooler8-g27 DOT priv DOT proxad DOT net> <48848513 DOT 1857571288894785382 DOT JavaMail DOT root AT spooler8-g27 DOT priv DOT proxad DOT net> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <48848513.1857571288894785382.JavaMail.root@spooler8-g27.priv.proxad.net> |
| User-Agent: | Mutt/1.5.20 (2009-06-14) |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| 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 Thu, Nov 04, 2010 at 07:19:45PM +0100, hules AT free DOT fr wrote:
>Some more info about that infinite loop in cygwin1.dll .
>
>This is indeed inside the cygheap_fixup_in_child function of cygwin1.dll .
>
>Inside this function, there is a loop that is:
>
>for (_cmalloc_entry *rvc = cygheap->chain; rvc; rvc = rvc->prev) {
> ...
>}
>
>In the case of my sh.exe process , this loop never ends because it is stuck with an "rvc" pointer that is such that "rvc->prev == rvc"
>
>I'm not sure what to look at, is there a chance that this is an "easy" bug to fix ?
Not unless you can provide a reproducible test case. If this is memory
corruption that's rarely an easy bug to track down.
It isn't clear why you can't use gdb to debug this, btw.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |