[solved] Corrupted project file

https://www.dacm-logiciels.fr/tracewin
Post Reply
Norwayyngvelevinsen
Initiated
Initiated
Posts: 34
Joined: Fri 5 Mar 2021 10:40
Location: ESS, Sweden
Country:
Norway (no)
Norway

[solved] Corrupted project file

Post by Norwayyngvelevinsen »

Hello,

I upgraded from tracewin 2.20.0.5 to 2.20.1.2 today. When I open TraceWin it opens my previously open project. I then after a couple of seconds get an alert that my project file is corrupted. When I click on OK it closes the application.
tracewin-corrupted-project.png
tracewin-corrupted-project.png (129.07 KiB) Viewed 2263 times
It's possible that the project file is corrupt somehow (how do I check?), but the behaviour is still problematic because it means effectively it is not possible to open any other project files or do anything with the software since it immediately closes. Deleting the configuration file is a workaround.

Downgrading to 2.20.0.5 works as well.

Project file attached.
Attachments
RFQ.ini
(43.77 KiB) Downloaded 138 times
Last edited by Norwayyngvelevinsen on Tue 7 Mar 2023 16:30, edited 1 time in total.
Norwayyngvelevinsen
Initiated
Initiated
Posts: 34
Joined: Fri 5 Mar 2021 10:40
Location: ESS, Sweden
Country:
Norway (no)
Norway

Re: Corrupted project file

Post by Norwayyngvelevinsen »

Forgot to mention, this has been tested on Manjaro Linux so far. I have not verified if the problem persist on other platforms yet.
User avatar
FranceDidier
Administrator
Administrator
Posts: 976
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: Corrupted project file

Post by FranceDidier »

Dear yngve,

It's nothing to do with the project file, but it's the executable that has been modified according to him (Checksum issue).
I've never had this one before and I wasn't expecting it.
Well normally the code should return an error code 3 or 4, are you able to tell me which one ?

Regards,

Didier
Norwayyngvelevinsen
Initiated
Initiated
Posts: 34
Joined: Fri 5 Mar 2021 10:40
Location: ESS, Sweden
Country:
Norway (no)
Norway

Re: Corrupted project file

Post by Norwayyngvelevinsen »

Aha, I didn't understand that so well then.

It returns a 4:

Code: Select all

% md5sum /opt/tracewin/TraceWin
45baf096f35d3021f01a7d00d2b99fa2  /opt/tracewin/TraceWin
% /opt/tracewin/TraceWin
% echo $?
4
Norwayyngvelevinsen
Initiated
Initiated
Posts: 34
Joined: Fri 5 Mar 2021 10:40
Location: ESS, Sweden
Country:
Norway (no)
Norway

Re: Corrupted project file

Post by Norwayyngvelevinsen »

So I figured out what happened with the help of your input. The packaging tool I use on my system (makepkg) "strips symbols from binaries and libraries", which I guess in this case modified the checksum. With previous versions this has not been an issue.

I disabled this option when packaging and now it works. Thanks!
User avatar
FranceDidier
Administrator
Administrator
Posts: 976
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: [solved] Corrupted project file

Post by FranceDidier »

oK indeed my sum :0a65fac494d5da78aba8d0a9ec342c40 for last version on website.
It is true that in the previous versions this verification was more ligth.
I confess I don't understand that you can modify the executables in this way, it seems strange to me, but what does it matter, do you have a solution?

Regards,

Didier
Norwayyngvelevinsen
Initiated
Initiated
Posts: 34
Joined: Fri 5 Mar 2021 10:40
Location: ESS, Sweden
Country:
Norway (no)
Norway

Re: [solved] Corrupted project file

Post by Norwayyngvelevinsen »

I have a perfectly working solution, no worries. Yes it's a bit of black magic to me as well, can't really give the technically accurate answer to why that is.
Post Reply