Access violations when using TSynLog + sllError about mormot2 HOT 9 CLOSED

Which debug format did you use?

You should use Dwarf 2 or 3.

from mormot2.

I am not able to reproduce your issue on Win32 or Win64 with Dwarf 2 debug symbols, and the current version of mORMot.

from mormot2.

Retried with last mORMot sources.

from mormot2.

I am not able to reproduce.

Try to debug more on your side.
What is the stack trace?
Where is the exact location?

And don't use a LCL UI, try with a console app.

from mormot2.

Tried without LCL UI and it works. So somewhere LCL introduces something the debug parser doesn't like.

Stack trace

from mormot2.

Can you debug in -O0 or -O1 level to have a more precise stack trace?

Some LCL unit may have weird/unusual symbols which failed our dbg parser.

Also try in Dwarf 3 format to see if it changes something.

from mormot2.

With Dwarf3, -O0 and fpdebug backend, I can't debug in TDwarfReader.ParseCompilationUnits. With gdb, I can step to step in this function, but I can't watch any variables. The issue seems in files[prevfile], but I can't see for which unit.

Anyway in this if

from mormot2.

That is very informative information!

Please try c21ee776

from mormot2.

It works! Thank you very much!

from mormot2.