Loosing Callstack on Aurelius-Exceptions

We got some exceptions while initiating our MappingExplorer for threadsafety on startup.

Right now, there is an AccessViolation occuring on runtime, not while debugging.
You are fetching this AccessViolation within TMappingExplorer.LoadMapping.

    for Clazz in Hierarchy.Classes do
      try
        FindEntityType(Clazz);
      except
        on E: Exception do
          raise EClassMappingFailed.Create(Clazz, E.Message, E.ClassName);
      end;

Could you raise an outer exception instead of raising another exception, loosing all informations like callstack.

    for Clazz in Hierarchy.Classes do
      try
        FindEntityType(Clazz);
      except
        on E: Exception do
          e.RaiseOuterException(EClassMappingFailed.Create(Clazz, E.Message, E.ClassName));
      end;

In this case it was your AccessViolation fixed within July 2025 patch:

  • Fixed: Sporadic Access Violation errors when running applications compiled with assertions off.

Ok, we will implement the modification.