X-Spam-Check-By: sourceware.org Message-ID: <43D52923.C90D9967@dessent.net> Date: Mon, 23 Jan 2006 11:06:11 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin Setup: Fatal Error: Uncaught Exception References: <43D467F0.4020706@tlinx.org> <43D46B88.FD612AE@dessent.net> <20060123112502.GB2188@efn.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Igor Peshansky wrote: > I've looked at this a bit. Here's the weird part: the error says > "Uncaught Exception", but all the throws of that exception appear to be > properly wrapped in try/catch blocks. So a simple "change exception into > an mbox" kind of solution won't work here. More debugging is needed. The reason for the box is that the md5 checking was changed to run in a different thread than originally designed (now in the main thread instead of the download thread IIRC) and that thread does not have any particular catch handler for that exception, only the TOPLEVEL_CATCH which punts with the generic error. Brian -- 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/