Simmo Saan

I don't recall ever having this issue before on this machine, which I've used for such runs for a long time. Only the last few (attempted) runs have started hitting...

The first `Errno 0` now happened: ``` 2025-11-13 15:34:54,589 - DEBUG - Killing process 2602259 due to out-of-memory event from kernel. 2025-11-13 15:34:54,648 - DEBUG - Waiting for process ./goblint_runner.py...

From the `Errno 0` time above: ``` Nov 13 15:34:54 goblint-new kernel: goblint invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0 Nov 13 15:34:54 goblint-new kernel: CPU: 5 PID: 2602289 Comm: goblint Not...

I'm not sure what the morally and scientifically right approach would be either. Doing the number comparisons on just the rounded results can yield to unexpected results as well. Somehow...

It's a draft because I think this simple thing also makes some cases less precise by not incorporating some query. It's probably fixable but the bigger question might be if...

> Usually accesses while single-threaded aren't even added to `allglobs`, but apparently the thread ID variable write in `pthread_create` is added although as if single-threaded. This is odd for two...

Something completely mysterious is happening with the fixpoint errors. Printing out the solver solution indicates the unknown being there, yet not being found. Printing `hash`es shows they match, so that's...

I've hunted the issue down to Apron's `compare` implementations not being suitable for `Set` and `Make`: https://github.com/antoinemine/apron/issues/99. I'm surprised that this hasn't shown up before. Or maybe it has and...

This was for an attempt to validate some witnesses with ghosts. Since we no longer plan to do this and because this didn't scale (or be precise enough, depending on...

I see. I opened an upstream issue then: https://github.com/pygments/pygments/issues/2975.