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 9410
legion_context.cc line 1238
legion_context.cc line 10557
legion_context.cc line 10565
legion_context.cc line 10573
legion_context.cc line 10580
legion_context.cc line 12839
legion_context.cc line 23615
legion_ops.cc line 5210
legion_ops.cc line 5248
legion_ops.cc line 5269
legion_ops.cc line 5299
legion_ops.cc line 5317
legion_ops.cc line 5331
legion_ops.cc line 5345
legion_ops.cc line 5366
legion_ops.cc line 6950
legion_ops.cc line 7028
legion_ops.cc line 7850
legion_ops.cc line 7889
legion_ops.cc line 7918
legion_ops.cc line 7929
legion_ops.cc line 7940
legion_ops.cc line 7952
legion_ops.cc line 7975
legion_ops.cc line 7993
legion_ops.cc line 14557
legion_ops.cc line 14568
legion_ops.cc line 16510
legion_ops.cc line 16813
legion_ops.cc line 16835
legion_ops.cc line 16850
legion_ops.cc line 16872
legion_ops.cc line 16889
legion_ops.cc line 16899
legion_ops.cc line 16924
legion_ops.cc line 21962
legion_ops.cc line 22278
legion_ops.cc line 22319
legion_ops.cc line 22337
legion_ops.cc line 22357
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 2662
legion_replication.cc line 2675
legion_replication.cc line 3075
legion_replication.cc line 3087
legion_replication.cc line 3290
legion_replication.cc line 3303
legion_replication.cc line 4401
legion_replication.cc line 4413
legion_replication.cc line 4447
legion_replication.cc line 5196
legion_replication.cc line 5456
legion_replication.cc line 5808
legion_replication.cc line 6377
legion_replication.cc line 7839
legion_replication.cc line 9742
legion_replication.cc line 15545
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 1624
legion_tasks.cc line 1775
legion_tasks.cc line 1797
legion_tasks.cc line 1871
legion_tasks.cc line 1920
legion_tasks.cc line 1943
legion_tasks.cc line 2794
legion_tasks.cc line 2851
legion_tasks.cc line 2973
legion_tasks.cc line 2982
legion_tasks.cc line 2993
legion_tasks.cc line 3013
legion_tasks.cc line 3021
legion_tasks.cc line 3101
legion_tasks.cc line 3141
legion_tasks.cc line 3167
legion_tasks.cc line 3176
legion_tasks.cc line 3200
legion_tasks.cc line 3217
legion_tasks.cc line 3235
legion_tasks.cc line 3244
legion_tasks.cc line 3260
legion_tasks.cc line 3281
legion_tasks.cc line 3641
legion_tasks.cc line 3647
legion_tasks.cc line 3657
legion_tasks.cc line 3760
legion_tasks.cc line 3769
legion_tasks.cc line 3782
legion_tasks.cc line 3796
legion_tasks.cc line 3807
legion_tasks.cc line 3818
legion_tasks.cc line 3836
legion_tasks.cc line 3849
legion_tasks.cc line 3872
legion_tasks.cc line 3900
legion_tasks.cc line 3922
legion_tasks.cc line 3935
legion_tasks.cc line 3944
legion_tasks.cc line 3958
legion_tasks.cc line 3971
legion_tasks.cc line 3981
legion_tasks.cc line 3993
legion_tasks.cc line 4020
legion_tasks.cc line 4031
legion_tasks.cc line 4046
legion_tasks.cc line 4459
legion_tasks.cc line 4475
legion_tasks.cc line 4515
legion_tasks.cc line 5298
legion_tasks.cc line 5310
legion_tasks.cc line 5322
legion_tasks.cc line 5341
legion_tasks.cc line 5356
legion_tasks.cc line 5830
legion_tasks.cc line 7456
legion_tasks.cc line 7466
legion_tasks.cc line 7713
legion_tasks.cc line 7982
legion_tasks.cc line 7991
legion_tasks.cc line 9635
legion_tasks.cc line 9651
legion_tasks.cc line 11090
runtime.cc line 8285
runtime.cc line 8300
fatal 2007
Message: unknown field ID #1 requested during instance creation
region_tree.cc line 13999
region_tree.cc line 14029
fatal 2009
Message: Local field creation is not currently supported for control replication with task #1 (UID #2)
legion_context.cc line 5531
legion_context.cc line 5658
legion_context.cc line 16833
legion_context.cc line 16963
legion_context.cc line 17137
legion_context.cc line 17242
legion_replication.cc line 12303
legion_tasks.cc line 3385
runtime.cc line 6274
runtime.cc line 6285
runtime.cc line 11368
runtime.cc line 11534
fatal 2011
Message: Dynamic Custom Serdez IDs exceeded library ID offset #1
runtime.cc line 19323
runtime.cc line 19697
runtime.cc line 19951
runtime.cc line 20206
runtime.cc line 20696
runtime.cc line 20929
runtime.cc line 21055
fatal 2012
Message: Dynamic registration callbacks cannot be registered after the runtime has been started with multiple runtime instances.
runtime.cc line 31424
runtime.cc line 31429
runtime.cc line 31443
runtime.cc line 31940
runtime.cc line 31971
fatal 2013
Message: Unsupported size #1 for consensus match in #2 (UID #3)
legion_context.cc line 12704
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 18028
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 16178
legion_analysis.cc line 16266
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 6797
legion_instances.cc line 1708
legion_instances.cc line 1715
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 3174
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 10371