description: The Firebird::PathName get_process_name() on Windows platform could lead into the following situation:

You have a plugin based software. The plugins placed into a directory below the main executable.
Just like this:

c:\program files\software - where the main executable resides
c:\program files\software\plugins - where the plugin modules (dll-s) resides

If one of the plugins uses the Firebird embeded version the client library (fbembed as fbclient.dll) placed into the plugin directory (c:\program files\software\plugins)
After the plugin loads the client library the GetModuleFileName(NULL, ....) gets back the main executable path. This is wrong because the fb located in the plugins directory.
The embeded fb client looks for all the necessary files (aliases.conf, firebird.conf, firebird.msg, UDF dir) in the main executable dir not where the actual client library resides.

Example:
c:\program files\software\main.exe - where the main executable resides

c:\program files\software\plugins - where the plugin modules (dll-s) resides
c:\program files\software\plugins\myplugin.dll (depends on firebird)
c:\program files\software\plugins\fbclient.dll
c:\program files\software\plugins\firebird.conf
c:\program files\software\plugins\firebird.msg
c:\program files\software\plugins\aliases.conf
...
c:\program files\software\plugins\udf

The GetModuleFileName(NULL, ....) returns c:\program files\software\main.exe not the c:\program files\software\plugins\fbclient.dll

=>

The Firebird::PathName get_process_name() (in src\common\utils.cpp) on Windows platform could lead into the following situation:

You have a plugin based software. The plugins placed into a directory below the main executable.
Just like this:

c:\program files\software - where the main executable resides
c:\program files\software\plugins - where the plugin modules (dll-s) resides

If one of the plugins uses the Firebird embeded version the client library (fbembed as fbclient.dll) placed into the plugin directory (c:\program files\software\plugins)
After the plugin loads the client library the GetModuleFileName(NULL, ....) gets back the main executable path. This is wrong because the fb located in the plugins directory.
The embeded fb client looks for all the necessary files (aliases.conf, firebird.conf, firebird.msg, UDF dir) in the main executable dir not where the actual client library resides.

Example:
c:\program files\software\main.exe - where the main executable resides

c:\program files\software\plugins - where the plugin modules (dll-s) resides
c:\program files\software\plugins\myplugin.dll (depends on firebird)
c:\program files\software\plugins\fbclient.dll
c:\program files\software\plugins\firebird.conf
c:\program files\software\plugins\firebird.msg
c:\program files\software\plugins\aliases.conf
...
c:\program files\software\plugins\udf

The GetModuleFileName(NULL, ....) returns c:\program files\software\main.exe not the c:\program files\software\plugins\fbclient.dll

description: The Firebird::PathName get_process_name() (in src\common\utils.cpp) on Windows platform could lead into the following situation:

You have a plugin based software. The plugins placed into a directory below the main executable.
Just like this:

c:\program files\software - where the main executable resides
c:\program files\software\plugins - where the plugin modules (dll-s) resides

If one of the plugins uses the Firebird embeded version the client library (fbembed as fbclient.dll) placed into the plugin directory (c:\program files\software\plugins)
After the plugin loads the client library the GetModuleFileName(NULL, ....) gets back the main executable path. This is wrong because the fb located in the plugins directory.
The embeded fb client looks for all the necessary files (aliases.conf, firebird.conf, firebird.msg, UDF dir) in the main executable dir not where the actual client library resides.

Example:
c:\program files\software\main.exe - where the main executable resides

c:\program files\software\plugins - where the plugin modules (dll-s) resides
c:\program files\software\plugins\myplugin.dll (depends on firebird)
c:\program files\software\plugins\fbclient.dll
c:\program files\software\plugins\firebird.conf
c:\program files\software\plugins\firebird.msg
c:\program files\software\plugins\aliases.conf
...
c:\program files\software\plugins\udf

The GetModuleFileName(NULL, ....) returns c:\program files\software\main.exe not the c:\program files\software\plugins\fbclient.dll

=>

The Firebird::PathName get_process_name() (in src\common\utils.cpp) on Windows platform could lead into the following situation:

You have a plugin based software. The plugins placed into a directory below the main executable.
Just like this:

c:\program files\software - where the main executable resides
c:\program files\software\plugins - where the plugin modules (dll-s) resides

If one of the plugins uses the Firebird embeded version the client library (fbembed as fbclient.dll) placed into the plugin directory (c:\program files\software\plugins)
After the plugin loads the client library the GetModuleFileName(NULL, ....) gets back the main executable path. This is wrong because the fb located in the plugins directory.
The embeded fb client looks for all the necessary files (aliases.conf, firebird.conf, firebird.msg, UDF dir) in the main executable dir not where the actual client library resides.

Example:
c:\program files\software\main.exe - where the main executable resides

c:\program files\software\plugins - where the plugin modules (dll-s) resides
c:\program files\software\plugins\myplugin.dll (depends on firebird)
c:\program files\software\plugins\fbclient.dll
c:\program files\software\plugins\firebird.conf
c:\program files\software\plugins\firebird.msg
c:\program files\software\plugins\aliases.conf
...
c:\program files\software\plugins\udf

The GetModuleFileName(NULL, ....) returns c:\program files\software\main.exe not the c:\program files\software\plugins\myplugin.dll

Link: This issue duplicates CORE1814 [ CORE1814 ]

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Duplicate [ 3 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

status: Resolved [ 5 ] => Closed [ 6 ]

QA Status: No test