fatal 2011
Message: Dynamic Custom Serdez IDs exceeded library ID offset #1
runtime.cc line 19307
runtime.cc line 19681
runtime.cc line 19946
runtime.cc line 20201
runtime.cc line 20691
runtime.cc line 20924
runtime.cc line 21050
fatal 2012
Message: Dynamic registration callbacks cannot be registered after the runtime has been started with multiple runtime instances.
runtime.cc line 31330
runtime.cc line 31335
runtime.cc line 31349
runtime.cc line 31846
runtime.cc line 31877
fatal 2017
Message: Found an internal garbage collection race. Please run with -lg:safe_mapper and see if it reports any errors. If not, then please report this as a bug.
legion_context.cc line 6841
legion_instances.cc line 1708
legion_instances.cc line 1715
fatal 2014
Message: Global registration callback function pointer #1 is not portable. All registration callbacks requesting to be performed 'globally' must be able to be recognized by a call to 'dladdr'. This requires that they come from a shared object or the binary is linked with the '-rdynamic' flag.
runtime.cc line 18012
fatal 2009
Message: Local field creation is not currently supported for control replication with task #1 (UID #2)
legion_context.cc line 5568
legion_context.cc line 5695
legion_context.cc line 16874
legion_context.cc line 17004
legion_context.cc line 17178
legion_context.cc line 17284
legion_replication.cc line 12316
legion_tasks.cc line 3386
runtime.cc line 6276
runtime.cc line 6287
runtime.cc line 11383
runtime.cc line 11549
fatal 67
Message: Mapper #1 specified a slice for a must epoch launch in control replicated task #2 (UID #3) for which not all the points mapped to the same shard. Legion does not currently support this use case. Please specify slices and a sharding function to ensure that all the points in a slice are owned by the same shard
legion_analysis.cc line 9371
legion_context.cc line 1273
legion_context.cc line 10601
legion_context.cc line 10609
legion_context.cc line 10617
legion_context.cc line 10624
legion_context.cc line 12878
legion_context.cc line 23687
legion_ops.cc line 5209
legion_ops.cc line 5247
legion_ops.cc line 5268
legion_ops.cc line 5298
legion_ops.cc line 5316
legion_ops.cc line 5330
legion_ops.cc line 5344
legion_ops.cc line 5365
legion_ops.cc line 6949
legion_ops.cc line 7027
legion_ops.cc line 7849
legion_ops.cc line 7888
legion_ops.cc line 7917
legion_ops.cc line 7928
legion_ops.cc line 7939
legion_ops.cc line 7951
legion_ops.cc line 7974
legion_ops.cc line 7992
legion_ops.cc line 14556
legion_ops.cc line 14567
legion_ops.cc line 16509
legion_ops.cc line 16811
legion_ops.cc line 16833
legion_ops.cc line 16848
legion_ops.cc line 16870
legion_ops.cc line 16887
legion_ops.cc line 16897
legion_ops.cc line 16922
legion_ops.cc line 21958
legion_ops.cc line 22274
legion_ops.cc line 22315
legion_ops.cc line 22333
legion_ops.cc line 22353
legion_replication.cc line 691
legion_replication.cc line 708
legion_replication.cc line 1077
legion_replication.cc line 1111
legion_replication.cc line 1127
legion_replication.cc line 1152
legion_replication.cc line 2665
legion_replication.cc line 2678
legion_replication.cc line 3078
legion_replication.cc line 3090
legion_replication.cc line 3293
legion_replication.cc line 3306
legion_replication.cc line 4404
legion_replication.cc line 4416
legion_replication.cc line 4450
legion_replication.cc line 5209
legion_replication.cc line 5469
legion_replication.cc line 5821
legion_replication.cc line 6390
legion_replication.cc line 7852
legion_replication.cc line 9755
legion_replication.cc line 15559
legion_tasks.cc line 773
legion_tasks.cc line 781
legion_tasks.cc line 856
legion_tasks.cc line 864
legion_tasks.cc line 919
legion_tasks.cc line 924
legion_tasks.cc line 1625
legion_tasks.cc line 1776
legion_tasks.cc line 1798
legion_tasks.cc line 1872
legion_tasks.cc line 1921
legion_tasks.cc line 1944
legion_tasks.cc line 2795
legion_tasks.cc line 2852
legion_tasks.cc line 2974
legion_tasks.cc line 2983
legion_tasks.cc line 2994
legion_tasks.cc line 3014
legion_tasks.cc line 3022
legion_tasks.cc line 3102
legion_tasks.cc line 3142
legion_tasks.cc line 3168
legion_tasks.cc line 3177
legion_tasks.cc line 3201
legion_tasks.cc line 3218
legion_tasks.cc line 3236
legion_tasks.cc line 3245
legion_tasks.cc line 3261
legion_tasks.cc line 3282
legion_tasks.cc line 3645
legion_tasks.cc line 3651
legion_tasks.cc line 3661
legion_tasks.cc line 3764
legion_tasks.cc line 3773
legion_tasks.cc line 3786
legion_tasks.cc line 3800
legion_tasks.cc line 3811
legion_tasks.cc line 3822
legion_tasks.cc line 3840
legion_tasks.cc line 3853
legion_tasks.cc line 3876
legion_tasks.cc line 3904
legion_tasks.cc line 3926
legion_tasks.cc line 3939
legion_tasks.cc line 3948
legion_tasks.cc line 3962
legion_tasks.cc line 3975
legion_tasks.cc line 3985
legion_tasks.cc line 3997
legion_tasks.cc line 4024
legion_tasks.cc line 4035
legion_tasks.cc line 4050
legion_tasks.cc line 4463
legion_tasks.cc line 4479
legion_tasks.cc line 4519
legion_tasks.cc line 5303
legion_tasks.cc line 5315
legion_tasks.cc line 5327
legion_tasks.cc line 5346
legion_tasks.cc line 5361
legion_tasks.cc line 5835
legion_tasks.cc line 7461
legion_tasks.cc line 7471
legion_tasks.cc line 7718
legion_tasks.cc line 7987
legion_tasks.cc line 7996
legion_tasks.cc line 9646
legion_tasks.cc line 9662
legion_tasks.cc line 11101
runtime.cc line 8299
runtime.cc line 8314
fatal 2018
Message: Something requested a very strange pattern for collective instance rendezvous with different points asking to rendezvous with different field sets on the same physical instance. This isn't currently supported. Please report your use case to the Legion developer's mailing list.
legion_ops.cc line 3173
fatal 2020
Message: Task #1 (UID #2) requested the creation of a dynamic collective while profiling for critical paths without recording all critical barrier arrivals. Critical path analysis with dynamic collectives requires that you use the '-lg:prof_all_critical_arrivals' flag.
legion_context.cc line 10415
fatal 2015
Message: Unsafe re-use of reduction instance detected due to alternating un-flushed reduction operations #1 and #2. Please report this use case to the Legion developer's mailing list so that we can help you address it.
legion_analysis.cc line 16152
legion_analysis.cc line 16240
fatal 2013
Message: Unsupported size #1 for consensus match in #2 (UID #3)
legion_context.cc line 12743
fatal 2007
Message: unknown field ID #1 requested during instance creation
region_tree.cc line 13972
region_tree.cc line 14002