Skip to content

Segfault in test 10 with GFortran 8.3.0 on macOS #422

Closed
@zbeekman

Description

@zbeekman

I suspect there is a memory leak, dangling pointer, or uninitialized variable somewhere. It can't be reliably reproduced (and could be a compiler bug) but if I run

ctest --repeat-until-fail 7 --schedule-random -j 12

on a macOS MBP with 6 physical cores & 12 logical cores I can usually get test 10 to segfault. Probably should throw valgrind at it on a linux box.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions