Skip to content

nbody: discover loop #4

Open
Open
@bennn

Description

@bennn

After injecting in nbody, the program got stuck in a loop.

Can we analyze stack traces (printed every 1k iterations or so) to find the stuck condition?

EDIT: low priority. As long as we can hand-analyze to find motivating examples, keep that up. Otherwise we bottleneck our research on solving another research problem (this one).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug-huntingFinding bugs with FloatTracker

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions