bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error reporting should be improved


From: Bob Friesenhahn
Subject: Re: Error reporting should be improved
Date: Tue, 29 Dec 2009 16:09:21 -0600 (CST)
User-agent: Alpine 2.01 (GSO 1266 2009-07-14)

On Tue, 29 Dec 2009, Peter Rosin wrote:

This is because the last error was overridden by the subsequent tries. Maybe we should stop trying once the right file was found. This way the right message could be given to user.

The trouble is that it is not dlopen that gives this message, it is
dlerror that gives the message, and it would be terrible to use
string comparison to dig out the cause of the failure. And that's
just for the dlopen loader, who knows how the other loaders behave
on obscure systems in wierd corner cases. Finding a reliable way
to catch all errors that are not "file not found" or equivalent
and quit early will not be an easy task.

The loaders typically just report CANNOT_OPEN when something fails,
and the ltdl core has no reliable way of knowing the underlying
cause.

Errors from the preopen loader can be overwritten, but the first error reported subsequent to the preopen loader should be retained. It seems like what we need is a flag that indicates if the error is allowed to be overwritten. The alternative is error message concantenation, but that might lead to ugly results.

Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]