Firebird 3.0.13 Win32 on Windows XP: binaries import GetThreadId (Vista+). Intentional drop or regression?

[Alex Smersi]

Hello,
We know Windows XP (and also Vista/7, etc.) is long out of support, but during internal legacy testing we noticed a breaking change with Firebird 3.0.13 (Win32) compared to 3.0.12.

On a Windows XP SP3 32-bit test VM:

• Firebird 3.0.3 → 3.0.12 installers complete successfully, and the ZIP kits can be used without issues.

• Firebird 3.0.13 fails immediately with: “The procedure entry point GetThreadId could not be located in the dynamic link library KERNEL32.dll”.

We reproduced and isolated the issue to the 3.0.13 Win32 binaries importing GetThreadId (Vista+). Using dumpbin on Windows 11:

• 3.0.12 fbclient.dll:

  • imports: no GetThreadId

• 3.0.13 fbclient.dll:

  • imports: KERNEL32.dll → GetThreadId

We also found other 3.0.13 Win32 files importing GetThreadId (e.g. firebird.exe, fbguard.exe, fb_lock_print.exe, plugins/engine12.dll, plugins/fbtrace.dll).
Note: gbak.exe did not import GetThreadId in our quick check.

Questions:

1. Could you please confirm (or deny) whether Firebird 3.0.13 intentionally drops the ability to run/install on Windows XP (and potentially other older Windows versions), due to the introduction of GetThreadId imports?

2. If this is an intentional/project decision (not a regression), is there an official/public statement (release notes, announcement, etc.) documenting the minimum supported Windows version for the 3.0.13 Win32 builds?

3. More generally, could you clarify the minimum supported Windows versions for the current major Firebird branches (3.0.x, 4.x, 5.x, and the upcoming 6.x), at least for the official Win32/Win64 binaries?

Thanks in advance.
Alex/

[Vlad Khorsun]

Questions:

1. Could you please confirm (or deny) whether Firebird 3.0.13 intentionally drops the ability to run/install on Windows XP (and potentially other older Windows versions), due to the introduction of GetThreadId imports?

  It was not intended. The usage of  GetThreadId() happens due to backporting fix #8403.

1. If this is an intentional/project decision (not a regression), is there an official/public statement (release notes, announcement, etc.) documenting the minimum supported Windows version for the 3.0.13 Win32 builds?

  There was intent to not broke support of WInXP 32-bit at least by fbclient. But there was no obligations, IIRC.

 

1. More generally, could you clarify the minimum supported Windows versions for the current major Firebird branches (3.0.x, 4.x, 5.x, and the upcoming 6.x), at least for the official Win32/Win64 binaries?

  FB4 should support WinXP 32-bit - same as FB3. FB5 and upper doesn't support WinXP anymore, it should be compatible with Win7.

Regards,

Vlad

[Vlad Khorsun]

Questions:

1. Could you please confirm (or deny) whether Firebird 3.0.13 intentionally drops the ability to run/install on Windows XP (and potentially other older Windows versions), due to the introduction of GetThreadId imports?

  It was not intended. The usage of  GetThreadId() happens due to backporting fix #8403.

 

  If you really need that compatibility - create a ticket, please. This case could be fixed.

Regards,

Vlad

[Alex Smersi]

Issue created.
https://github.com/FirebirdSQL/firebird/issues/8850

Many thanks.
Alex/

--
Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:
https://www.firebirdsql.org/donate
---
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/firebird-support/7e793dba-d8da-4eca-a4ec-e669721fdda4n%40googlegroups.com.