X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Heiko Elger Subject: Re: "Bad address" error while building cygwin with make -j2 Date: Thu, 15 Dec 2011 05:43:11 +0000 (UTC) Lines: 20 Message-ID: References: <4EE8E58C DOT 3000904 AT gmail DOT com> <20111214182757 DOT GA6392 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Christopher Faylor writes: > > It's easy to reproduce. It's the result of changes I made in recent snapshots > to handle signals in threads. > that sounds good. Is it easy to fix it! Is it fixed in latest snapshot 20111214? I read somthing about signal handling in ChangeLog. regars Heiko -- 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