mORMot Open Source

Hafedh TRIMECHE

Member

Registered: 2016-09-18

Posts: 32

External SIGSEGV SynCommons.pas

FPC: 3.3.1 (Trunk)
Lazarus: 2.0.10
SynCommons: 1.18.6093

Project xxxxxx raised exception class 'External: SIGSEGV'.

 In file 'D:\Developer\lib\mORMot\SynCommons.pas' at line 51119:
fElemType := PPointer(fElemType)^;

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,242

Website

Re: External SIGSEGV SynCommons.pas

Please provide a minimum reproducible example to guess the execution context.
(not putting code in the forum directly)

We don't use FPC trunk yet - it is sometimes too much unstable.
We use FPC 3.2 and Lazarus 2.0.10 on production as of today.
Check https://synopse.info/files/html/Synopse … l#TITL_203
You may need to tweak the Synopse.inc conditionals to fit your compiler version.

Hafedh TRIMECHE

Member

Registered: 2016-09-18

Posts: 32

Re: External SIGSEGV SynCommons.pas

Please not that switching to FPC 3.2 and Lazarus 2.0.10 raised another  exception related to CustomAttributes. I think that this functionality is only available under Trunk.

Error: Identifier not found "TCustomAttribute"

Best regards.

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,242

Website

Re: External SIGSEGV SynCommons.pas

Your path configuration is likely to be broken.
I guess there is something wrong with your include files, especially Synopse.inc.

Hafedh TRIMECHE

Member

Registered: 2016-09-18

Posts: 32

Re: External SIGSEGV SynCommons.pas

The Path to Synopse.inc is included into [Include files (-Fi)]: ..\..\lib\mORMot and [Other unit files (-Fu)]: ..\..\lib\mORMot

It works with the Trunk Branch!

Would you please provide a unit into which the TCustomAttribute is used?

Best regards.

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,242

Website

Re: External SIGSEGV SynCommons.pas

We don't use it anywhere in the core framework.
Are you really not able to compile TestSQL3.dpr?

Please provide a minimum reproducible example to guess the execution context.
(not putting code in the forum directly)
You didn't even state which source code line was involved, nor the OS used.