[Top][All Lists]

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

Re: Error reporting should be improved

From: Peter Rosin
Subject: Re: Error reporting should be improved
Date: Tue, 29 Dec 2009 22:00:43 +0100
User-agent: Thunderbird (Windows/20090812)


Den 2009-12-27 09:13 skrev Xiaoqiang Zhou:
I was using libtool to load a library which has unsatisfied

What version of libtool? On what system?

dependencies. libtool tells me that "file not found" while dlopen gives the correct message "undefined symbol".
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

At least, that's my take on the situation...


They are in the crowd with the answer before the question.
> Why do you dislike Jeopardy?

reply via email to

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