Curious Behaviour

[Chris Ahrendt]

Vitaliy Margolen wrote:
> Chris Ahrendt wrote:
>> When I turned on the debugging flag +ntdll  I noticed a rather strange 
>> behavior in wine. But before I open a bug on it I wanted to understand
>> how the shared libraries that emulate the various windows dll's are 
>> handled. When I turned on the +ntdll flag I started getting several file
>> not found errors in the logs as it searched for the dll's... One such 
>> example is advapi32.dll. This is handled by the shared library file of 
>> the same name.  Shouldn't the dll loader recognize this as a SO and 
>> return the fact it found it???
> 
> Everything is perfectly normal. Wine has number of places where it looks for
> builtin then native files (if builtin wasn't found). Of course usable file
> will exist in only one place.
> 
> Vitaliy
What about this part of the question as well...

This occurs on non built in DLL's :

I also noticed another bit of weirdness as well...  If the application
loads the "COMCTL32.dll" file or the "Comctl32.dll" it wont find it
but if it loads comctl32.dll it does. Now I know this is partially the
way the file system handles the files, but shouldn't it find the file if
it exists even with the capitalization screwy? It doesn't seem to happen
that often the ones I have noticed the error occurring are :
Comctl32
COMCTL32
msvcrt
MSVCRT
msvfw32
MSVFW32
WS2_32
ws2_32


I am just wondering if because of the above some of the weirder errors
we are seeing might be caused by this? Or at the least are filling up
trace logs when they don't need too...


Chris