https://bugs.freedesktop.org/show_bug.cgi?id=45364

--- Comment #4 from Heinz Repp <[email protected]> 2012-01-30 08:56:48 PST ---
(In reply to comment #3)
> If I read the web page you pointed to correctly, in all cases the directory
> from which soffice.bin is loaded is searched first, and that is where our
> libeay32.dll is located, isn't it? What am I missing?

Reread the page, and yes, you are right, and I was wrong thinking the cause was
there. So I dug a little deeper and found:

I see this happen with 2 DLLs, libeay32.dll and ssleay32.dll. They are not
loaded from the start, but get loaded when the help browser gets called. With
sysinternals' procmon I can see in which directories soffice.bin looks for
them. They are:

<installdir>\Basis\program\python-core-2.6.1\lib (1)
%windir%\system32 (2)
%windir%\system (3)
%windir% (4)
<installdir>\URE\bin (5)
and then all PATH entries in order (6)

This is exactly the order listed if SafeDllSearchMode is enabled, where we
expect:

(1) is the directory from which the application loaded
(5) is the current directory

but, looking at soffice.bin's environment through sysinternals' process
explorer, I see still:
the program's path is <installdir>\program\soffice.bin
its current directory is <installdir>\program\

The help browser isn't started in its own process but as a thread of
soffice.bin (using CreateThreadEx), so the kernel should honor soffice.bin's
settings, but somehow it picks the python-core/lib directory as application
load dir (because _ssl.pyd loads from there?) and URE\bin as current dir (?).

It looks as if the kernel is not doing what it should according to MS'
definitions, but somehow I feel the culprit might as well be with LibreOffice
tricking some environment settings when loading the help browser?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to