Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing leaves goblint_temp_* directories around #250

Closed
sim642 opened this issue Jun 15, 2021 · 1 comment
Closed

Crashing leaves goblint_temp_* directories around #250

sim642 opened this issue Jun 15, 2021 · 1 comment
Assignees

Comments

@sim642
Copy link
Member

sim642 commented Jun 15, 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.

@sim642
Copy link
Member Author

sim642 commented Jun 18, 2021

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 sim642 changed the title Crashing leaves goblint_temp_* directories next to input file Crashing leaves goblint_temp_* directories around Jun 18, 2021
@sim642 sim642 self-assigned this Jan 17, 2022
@sim642 sim642 closed this as completed in 39c7334 Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant