To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87730 Issue #|87730 Summary|OOo executables can find wrong DLLs Component|framework Version|DEV300m4 Platform|PC URL| OS/Version|Windows, all Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from [EMAIL PROTECTED] Wed Apr 2 09:36:50 +0000 2008 ------- On Windows, OOo executables (soffice.bin, unopkg.bin, etc.) are called with URE\bin and Basis 3.0\program directories added to the front of PATH, so that the DLLs against which the executables are linked are found. However, the Windows search order for DLLs is to look in the current working directory before looking in the PATH. If the current working directory happens to contain DLLs with the same names as DLLs contained in URE\bin or Basis 3.0\program, the OOo executables will erroneously pick up those bad DLLs, with arbitrary consequences. (This has happened when using an older-milestone testtool with a later-milestone soffice.) The best solution is probably to change the OOo starter executables (soffice.exe, unopkg.exe, etc.) to call the secondary executables (soffice.bin, unopkg.bin, etc.) with a "harmless" current working directory (e.g., the brand layer program directory where the executables are located). Changing the current working directory this way, of course, has consequences when the secondary processes (soffice.bin, unopkg.bin, etc.) receive relative filepaths/URLs (typically on the command line) which they are expected to make absolute relative to the current working directory. This is similar to how a second soffice.bin makes its command line arguments absolute today before piping them over to a first soffice.bin (desktop/source/app/officeipcthread.cxx:1.58 l. 503 ff), and can probably be consolidated in the following way, keeping the starter executables simple: In both cases (soffice.exe calling soffice.bin, and second soffice.bin piping to first soffice.bin), send any relative command line arguments unmodified, but also send the original current working directory, so that the receiving end can correctly make absolute arguments from relative ones. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
