[bug #4710] Opening non-existing store class

[nobody]

=================== BUG #4710: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4710&group_id=30

Submitted by: ogi                     Project: The GNU Hurd                 
Submitted on: Mon 08/11/2003 at 15:56
Category:  None                       Severity:  5 - Major                  
Priority:  None                       Bug Group:  None                      
Resolution:  None                     Assigned to:  None                    
Originator Name:                      Originator Email:                     
Status:  Open                         Reproducibility:  Every Time          
Size (loc):  None                     Effort:  0.00                         

Summary:  Opening non-existing store class

Original Submission:  This is part of mail exchange with Roland.  Although the 
complete fix requires changes in glibc, we'll still need to change the Hurd 
itself afterward.

>>$ ./store x:x # This test program calls store_typed_open.
>> ./store: cannot load libstore_x.so.0.3: libstore_x.so.0.3: cannot open 
>> shared object file: No such file or directory
>> store_typed_open: Function not implemented
>> 
>> This is printed in libstore/module.c:open_class when there is error and it 
>> is not ENOENT.  It seems that dlopen doesn't return ENOENT when shared 
>> object is not found.

I don't think dlopen actually sets errno reliably, or is required to.  So the 
kludge there doesn't even work.  Note it's marked with XXX because I knew it 
sucked when I wrote it.  Unfortunately I think the only correct thing to do is 
always eat the error message, or perhaps display it only with some runtime 
debugging option turned on by the user.  It would be nice to be able to see 
errors from a bogus module that doesn't load properly, but the situation where 
you can't distinguish that from a missing module is the same e.g. for nss 
modules.





No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4710&group_id=30

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/