On Tue, May 14, 2024 at 11:43:29AM +0100, Chris Lamb wrote: > Ah, I was hoping that the systemd slice apparatus would be able to > contain any traceback, but now that I think of it, being OOM-killed is > not quite the same as CPython-level crash (and thus traceback).
:) > > https://tests.reproducible-builds.org/debian/artifacts/r00t-me/trixie_i386_dasel_tmp-kqFaQ/ > > is maybe working as in crashing for you? > > Alas, this works for me and does not crash. I suppose the next thing > might be to try and run with --debug? That way, we might be able to > determine which file, comparator or external tool was being run when > diffoscope invoked the ire of the oom-killer. I'm not sure how --debug output should survive, but you mean just running diffoscope with an added --debug option? -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The average US president has been charged with 2 felonies: #45 with 91 and the others with 0.
signature.asc
Description: PGP signature
