From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Wed Feb 03 1999 - 13:23:42 EST
On Feb 3, 1999, Godmar Back <gback@marker.cs.utah.edu> wrote:
> Pat says he got this failure once. Then he rebuild and reinstalled
> everything and the failure went away, so he blamed bad interactions
> with the make install target for it. So we should exclude this as
> a possible reason.
My install tree is empty, so make check is (should be) picking
everything from the build tree.
> Ignoring that we may not properly protect calls to libltdl for a minute,
> the failure for you occurred even in the single-threaded case, did it not?
Yep
> Does libltdl use any signals for itself?
Nope, but a VTALRM during open() might cause it to return EINTR, for
example. But libltdl only uses fopen(), which should hide this
anyway... I don't know what may be going on, I just know that I'm
getting these random failures on Linux since the setjmp revolution.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:56 EDT