Cygwin Setup: Fatal Error: Uncaught Exception

Igor Peshansky
Mon Jan 23 19:56:00 GMT 2006

Moving to cygwin-apps, as this is likely to get technical.

On Mon, 23 Jan 2006, Brian Dessent wrote:

> 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.

Do you mean packagemeta::ScanDownloadedFiles() calling
packageversion::scan(), which calls check_for_cached()?  Then yes, this
isn't properly wrapped in a try/catch.  I'd like to verify that this is
the culprit (when someone sends me the corrupt tarball), but I think I see
a proper fix for this.  Will submit a patch shortly.
      |\      _,,,---,,_ |
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

More information about the Cygwin-apps mailing list