How to find out where burst native code from?

Hello everone.
I got some crash report recently, both Player and Editor have no dump file. (Tried Windows force dump but not work.)
Today i find an editor log like

=================================================================
	Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

=================================================================
	Managed Stacktrace:
=================================================================
	  at <unknown> <0xffffffff>
	  at Unity.Entities.UnmanagedUpdate_0000164F$BurstDirectCall:wrapper_native_indirect_00000278F4C047F0 <0x000b9>
	  at Unity.Entities.UnmanagedUpdate_0000164F$BurstDirectCall:Invoke <0x000ba>
	  at Unity.Entities.WorldUnmanagedImpl:UnmanagedUpdate <0x0008a>
	  at Unity.Entities.WorldUnmanagedImpl:UpdateSystem <0x0063a>
	  at Unity.Entities.ComponentSystemGroup:UpdateAllSystems <0x005ba>
	  at Unity.Entities.ComponentSystemGroup:OnUpdate <0x0013a>
	  at Unity.Entities.SystemBase:Update <0x006de>
	  at Unity.Entities.ComponentSystemGroup:UpdateAllSystems <0x006d5>
	  at Unity.Entities.ComponentSystemGroup:OnUpdate <0x0013a>
	  at Unity.Entities.SystemBase:Update <0x006de>
	  at DummyDelegateWrapper:TriggerUpdate <0x000e3>
	  at System.Object:runtime_invoke_void__this__ <0x00187>
=================================================================

How can i find the real function? Or where could find brust complete log to match these code?

Hope for help. TY.

The crash is happening in unmanaged (C++) code so a full stacktrace will unlikely to provide more meaningful info. But nevertheless, the only way to get the callstack info is to use a debug build with debug symbols, respectively a release build with separate debug symbols that must match the built (published) executable.

Cloud Diagnostics provides you with tools and instructions to get more info out of these crash reports.

Note that the process of generating symbols and later “symbolicating” the crash report differs depending on the platform.