I'm using ab09nd to reduce systems. Mildly by accident we are putting in a large system and choosing inputs/outputs that don't touch any of the dynamics. The function correctly reduces the system to size zero on output, but for some reason this now causes a segmentation fault.
I've compiled Slycot with -fcheck=all -fbacktrace -Og -g -Wall, but the segfault only occurs after garbage collection, and will occur immediately if you force collection using 'import gc; gc.collect()'
somehow this output case needs to be handled better by f2py or the wrapper instructions.
Attached is a yaml file with the system A,B,C,D that triggers the bug when run with dico = 'C', job = 'B', equil = 'S'
debug_ab09nd.txt