This is the mail archive of the
mailing list for the Cygwin project.
RE: 1.5.14-1 cygwin1.dll could not be found
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin-apps at cygwin dot com>
- Date: Mon, 18 Apr 2005 04:14:07 +0100
- Subject: RE: 1.5.14-1 cygwin1.dll could not be found
>From: Igor Pechtchanski
>Sent: 15 April 2005 19:42
> On Fri, 15 Apr 2005, Dave Korn wrote:
>> 5) Do I really need to worry about putting return statements after
>> calling "LogSingleton::GetInstance().exit (1);" ? There was a reference
>> in there to some kind of 'issue' with ::exit, but I haven't yet done an
>> archive search to try and understand what's going on - does anyone
> IIRC, gcc needs to know that the exit() function never returns. It does
> know for ::exit() (because there's an appropriate attribute on it), but it
> doesn't for LogSingleton::exit(), and so will complain that the functions
> are missing a return statement. So you need to put those in to quell the
Ok, that means I can throw away the early-exit indication code. I'd have
used 'abort' or 'exit' calls rather than return, myself; it makes it clear
to both compiler and user that a noreturn function has been called. That
simplifies the patch nicely.
Meantime I just found a rather evil bug that needs patching. More later.
Can't think of a witty .sigline today....