Skip to content

Segmentation fault at garbage collection after running ab09nd with return value of nr=0 #242

@mccullerlp

Description

@mccullerlp

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions