[Lazarus] Question

[wkitty42 at windstream.net]

On 12/21/21 3:15 AM, Евгений Кадисов via lazarus wrote:
> Thank you once more. It turned out that the problem was not solved. When I have 
> (2.0.12 instead of 2.0.10) [...]

perhaps looking at the changelogs for the differences between these two versions 
will help you find what you need to change in your program so it will work 
properly for your expected output?

i've spent about 15 minutes looking around so i might provide you a link to the 
changelogs but i'm unable to easily find them... sadly, the changes to the 
debian/changelog file provide no real information other than the version number 
being changed...

so i've dug deeper... looking on the lazarus SF site, i was finally able to find 
the commits for those two versions... with this information, we should be able 
diff them to find the difference(s) that may be causing your program troubles...

   ae9017    2.0.10
   871307    2.0.12

if you have a full git repository, you can diff these two with

   git diff ae9017..871307

however, the following command will list all of the commits between ae9017 and 
871307, inclusive... this may be an easier route to go to find what commit has 
lead to your situation...

   git rev-list --ancestry-path ae9017^..871307

this gives me, on my fresh clone, the following raw commit hash list of 76 
commits... they are listed from newer to older... the bottom one is the one that 
set the version to 2.0.10 (where you were) and the top one is the one that set 
the version to 2.0.12 (where you ended up)...

   87130707e7b820ae7167900041f9ea21087f2015
   9c41034dda9369ea03e24d1cc87d919a43ba5699
   0501f61b9bd61bd0af43802cf6ae8478b4540e19
   6a91ceb313ed2d98e5997ecbb44a354dd928fe5d
   0fc756f057705612f85b619a09faa39074137ba2
   128960ee5dc7b506f6085a32670e642e659a07d4
   815e3dc6d67ed3b82cfed51d8e6ee68c19dbf996
   48ffd9739cfee3aa6a2ca5fb0fd4fee7a6702459
   f7aa0270f144dcf23dac499ca64cfc1d8cde32d9
   17f21607562f81144161a19da7c7a57e1bc73dda
   77ecaa085694f99f38422dbacd01cb366364c314
   65acd97bcd3bf2c7f936a9dde4c66342a582f236
   8ae7b2bb457f6e820d9830eae2dbe6b0fcc82be8
   240db20a1df4b627eb08fcf4173e18157b739019
   2961d09e9e1c037cdfccec76a497e676925ddc08
   2c03a634c538289b4adb59b46a421e23dc97d92f
   561d01f2e6e12099448bd1137ede5d2aadeb4df2
   7c386df181505370de67a479a80783ff5fe8c4a1
   9b78caaf21fae9724ed9f9114457b6efef969cc5
   c00cb12cca382e57035586b67838feb44538e0ef
   ee6fa154ed0c2af13f82250d274eb14af058e1ba
   19aad3af455164815b82d4bc37bdc2659cb30b72
   77b7cb7d6171ba101a43957ec3d88d7eff7aa6b3
   69c095d1e2adc7f7f9e5a697547f2c13a5f441e3
   3e0f2f5e68b19313aa17f9d400368d7f390eb729
   c476a94462550eaff34b932a47797798a0231523
   8bf9b7f784eabf68bf9a40a87a34a93e49ed5f94
   8a0f57666f8e6c687b6b1c7dfed535cbfd9cca72
   2889401bd2fd5203e783c6dfdaaa5351bb10493b
   f29f662333bbd277b242d3f82d58b141257f26cc
   770bee475c8fda95eec53dc82a5c35ea88351aff
   f464a500fc618514ab1a5dd24b2e95e70b57539f
   36319f66d58c2b646db6b6a4d0e8d14167b80768
   a6e6e910f0eec6862de16e6aab0fcfeffb3ac671
   18ff8c47009eb874541e3bb69c0e2f54a80f4941
   90cbe5eed994dd1743b0e36c8180894c633cc34a
   c3e8aa2edff6559abf45f43df5bde550b97d1200
   3bb8fe51b51eca80430b07b6a7c3181659496e9e
   5d06959c361fdea9b32a0823ebc8b3f7f18343f1
   8ddcd102ee193cb4289ec2e2aa85a54e6c2bdf94
   c910891f1b64865ca203a16636ce810809be7474
   ebab00eb5b8ac37b2d3daf60d85318c187a17dbd
   886ab5f015ba66d71cf24f7773195400f0bd10cd
   d6eb3f3a05bff9ec84e98b5a27f3609698997be1
   f7c69baac6b2c088660674d178d682af744f1d0c
   2838eb631edeb4bc450043e8a747b51227796b12
   0c525d92226f4b22e0f77b35d7e18b22d433f193
   7b2dec7cc7e6ae765ccf5fc750eb4fe874902b58
   99021f5b35481decda4130b18d18375b34948e56
   d7ef338ff6a6c709afd6f214828336034d787906
   8e84940d5c2fbb4c498aa62cd95195fb00b26f10
   b85943b8636152ca286cbaed38bbc605f8a87083
   7382f9906d344397b37c8c583acc8842349006f1
   b1e194c219563707d0fb161e6d71fdabb50abe75
   036336f93dde2058b1c3afd6ad53a759b6cf9092
   5a9fdda475102679a45bb8afa8be569864a4a356
   ed18ef848631e0c5bbad38f5bf9ffef3a72ab5cd
   7b87b59dda416573e4796d080027ffab0348dd5f
   e400755e2bf56c5dd6ddebca5270da61a1e6cb98
   08002f607e7451f104b1e46f529c3bfec7cf9cee
   80f42df3c7a5aefc348bccfc1b431de21c457fff
   918ae6195764b5f060f7c891996f98d6d604bf28
   9a2223b8b20f21a82fa60a8550cf006410e5e0ae
   d6c010f5a8c0c31ec1a1516589c1b92f69816a81
   e544c76cd565c32fd329751e18951cd0b77f32e5
   d4e099a4f3e962760f254210cdc5dd3bbd52811b
   bda8742a72427fc72a333cc145d9a20b5de7dfe2
   764bbbc59c6db0564166e4d61f729501a0ee2870
   efa348b3c513888855b79671efa7c8832f318838
   53025b32f9736f37b3feb0967d4fc42b129738bf
   0e06f0d9e1fa5b6f761d6bd4bbd4d3bf8f422b7a
   bee446707f7308b9c2772085512030cce92c89b1
   90bde32386685bf9675c506c9479a054ceed4b63
   7d81afac5da07c0c5a47503fe30682bd36e818cf
   eb4b5f979ecd00f9e0856090ee2855aa750dad21
   ae9017d9a9b821dfed143169da8b59a0613335c8


assuming you are using UTF-8, i do find a few UTF-8 related commits and some of 
those are related to the version of FPC being used... so that brings the 
question of which FPC are you using behind your Lazarus?

using this command line, i find these 5 commits which may lead you in the right 
direction...

   git log --pretty=oneline ae9017^..871307 | grep -Ei -e "UTF-?8"

   d6eb3f3a05bff9ec84e98b5a27f3609698997be1 TUTF8Process: workaround for the 
poNoConsole->poDetached change. Better hacks for old FPC versions without 
TProcessClassTemplate. Issue #35991

   f7c69baac6b2c088660674d178d682af744f1d0c LazUtils: Dont override 
TProcess.Execute for TProcessUTF8 starting from FPC 3.2. Issue #35991

   2838eb631edeb4bc450043e8a747b51227796b12 LazUtils: Delete very old code for 
TProcessUTF8 that was needed for FPC 2.x.

   7b2dec7cc7e6ae765ccf5fc750eb4fe874902b58 lazutils: Try to minimize (NOT a 
fix) the risks of TProcessUtf8 crashes. Crash introduced in r50595 #d0dace2bf5 
for Issue #28991

   d7ef338ff6a6c709afd6f214828336034d787906 Merged revision(s) part of 63978 
from trunk: FpDebug: fix opening files with utf8 name on windows. Issue #37884 
........


*NOTE:* i am not a git guru... the above commands were found via uncle google... 
i may be missing some commits in my list(s) above... but i think not when i look 
at the repo using a graphical git tool (giggle and gitk) that shows me the tree 
of commits in the Lazarus main (svn trunk?) branch... i can only hope that this 
helps somehow and made lead to a solution for you without having to try to drop 
back to an older version of Lazarus (and possibly FPC)...


-- 
  NOTE: No off-list assistance is given without prior approval.
        *Please keep mailing list traffic on the list where it belongs!*