mORMot Open Source

@trx
If you are willing to share your efforts, I would be very pleased.

Please have a look at your fpc.cfg. Fpcupdeluxe might have added a -WM define (somewhere at the bottom of the cfg). You might try to remove it and build the mORMot again. I do not know if it will improve anything, but its worth the try.

Just for your info. The bug-report related to this FPC 3.2.2 issue. Conclusion: FPC 3.2.2 is not suited for the mORMot[2] due to this bugger.
https://gitlab.com/freepascal.org/fpc/s … sues/39438

Don't worry. You are not wasting anybody's time.
You gave good info. Except for the manner in which you installed the mORMot2.
So, how did you install mORMot2 ?
With this info, I will try to reproduce your issue.

With FPC trunk and mORMot2 from just a few minutes ago, I cannot reproduce your errors.
All greens on my system: win11, mORMot2 for win32 and win64.

Bugger solved.
https://gitlab.com/freepascal.org/fpc/s … 1dfbc523a8

All greens now on Linux AArch64 with FPC trunk. Very good !
However, a small workaround for the FPC source parser was needed.
In function GetJsonField, a label (lit) is used for a goto. This results in code errors on AArch64.
If the label is removed, all is ok and 100% error free mORMot2 can be enjoyed.

Should be within a week. Still waiting for confirmation of some fixes.

@ab

Yes !

Update about FPC trunk + mORMot2 on AArch64 (Odroid C2 running Arch Linux).
The memory leak reported by me earlier seems to be caused by FPC. Even Lazarus crashes (and gets killed) due to huge and increasing memory consumption, even when idle.
Will keep you informed.

I can confirm the described problem(s) on aarch64. And, I have a hard time debugging the issue(s).
At the moment, most severe problems (on my system) stem from a memory leak on fastsetstring (and derivatives). String-memory is not released, causing a (out-of-memory) system-crash.
Still looking into this. Will report if any news.

There ae some more (also runtime) errors on Windows with latest sources.
I am looking into them right now. Nearly all solved. Stay tuned. Will do a pull-request.

Just tested with FPC 3.2.3
Same problems still seem to be present unfortunately.

It would be nice if you could share the changes that were needed to get things working again.
Thanks !

Nice find. This is good to know ! Lets try to use this "feature" ...

As an in-between test, you could add the EchoRecord function into mORMot1.18 and see if it works with that version.
(skip this post if it is already there)

You report an error. I did have a look at this error. And tested the mORMot2 with FPC trunk. On my system, the error seems to be related to a particular statement. If the same is valid on your system, you have helped us in isolating this error. And making the bug-hunt and bug-solving a bit easier. If the bug is fixed, the test-suit will run again at 100% greens.

I guess and hope you mean FPC 3.2.0 ?

Crossing from win64 to win32 is very ill advised and not supported by both FPC and mORMot[2].

As I am myself running the mORMot[2] with FPC trunk on various systems, it would be interesting (for me) to see your results when using trunk.

As a sidenote: with trunk I am also experiencing some errors with Core Script at 3.1 ! Its caused by this line (test.core.script.pas):

v := Run('Date() + "=" + new Date().toString()');

If I comment this line (and the accompanying next line), the tests run fine.

I guess L_VV compiles with FPC trunk.
https://synopse.info/forum/viewtopic.ph … 542#p34542

Try this:

if not Assigned(OnMatch) or
    (not (Assigned(KeyCompare) or
    Assigned(ValueCompare))) then
  exit;

Hi Ab,
At the moment, mORMot2 does not run on arm. It gives a "property has no RTTI"-error. Naturally, this can be solved.
The question however:
Is mORMot2 suitable and mature now to perform deep debugging these errors ? If yes, I will dig into this and start porting my apps towards mORMot2.
Thanks.

Thanks very much. Will look into this. I guess this will serve my needs.

Teasing presentations !! Clear explanations also. Looking forward to mORMot2.

Some (better) improvements might be expected from the advices that are shown here:
https://www.sqlite.org/compile.html