You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just started running Goblint on a bunch of benchmarks using the goblint/bench script and whenever Goblint crashes (due to some exception), the goblint_temp_* directory stays around in the middle of the benchmarks. It's quite inconvenient because if the benchmarks are version controlled, it looks like there's new (temporary) files to commit.
They should either be cleaned up, not to pollute paths that are being analyzed. Alternatively, those temporary directories shouldn't be created next to the input file, but into the system's temporary directory using corresponding APIs.
The text was updated successfully, but these errors were encountered:
Small correction: the goblint_temp_* directories are actually created in the current working directory. It's the bench repo script which just cds to each benchmark's directory before running Goblint.
sim642
changed the title
Crashing leaves goblint_temp_* directories next to input file
Crashing leaves goblint_temp_* directories around
Jun 18, 2021
I just started running Goblint on a bunch of benchmarks using the goblint/bench script and whenever Goblint crashes (due to some exception), the goblint_temp_* directory stays around in the middle of the benchmarks. It's quite inconvenient because if the benchmarks are version controlled, it looks like there's new (temporary) files to commit.
They should either be cleaned up, not to pollute paths that are being analyzed. Alternatively, those temporary directories shouldn't be created next to the input file, but into the system's temporary directory using corresponding APIs.
The text was updated successfully, but these errors were encountered: