This is because ld flag parsing is too restrictive and we're falling back to version detection via looking at the binary contents. This is a fairly large binary (~217 MB) so there aren't good odds at finding the correct version generically this way. The change made in this PR is to loosen the LD flag parsing regex to allow for discovering *ReleaseVersion= arguments.
TiDB server is showing the incorrect version:
This is because ld flag parsing is too restrictive and we're falling back to version detection via looking at the binary contents. This is a fairly large binary (~217 MB) so there aren't good odds at finding the correct version generically this way. The change made in this PR is to loosen the LD flag parsing regex to allow for discovering
*ReleaseVersion=
arguments.