Open omentic opened 1 year ago
https://github.com/nim-lang/Nim/issues/20450
There were lots of segfault issues with Nim I saw apart from this one affecting Pakku directly around this time that were mentioned in the nim-lang issues due to massive changes taking place for v2. Most of those issues were presumably fixed so hopefully this is something that will go away on Nim upgrades. I've never had this with nim-git which I mostly use at whatever commit I last built it at, although the PKGBUILD for nim-git is currently awaiting updates due to more Nim changes, there is a workaround here:
https://forum.nim-lang.org/t/10012#65990
Segfaults could depend on what hardware, os or related software and version is in use, especially intermittent ones. It might be worth trying nim-git to see if it happens there though first, as it could already be fixed.
And here on this issue: https://github.com/zqqw/pakku/issues/27 The last comment mentions 1.6.10 segfaults with pakku, it's a known issue but I think Nim development has already gone past that, it's just unfortunate the faulty old version has gone into the Arch repos but well, it happens.
an issue from hell :star_struck:
see https://aur.archlinux.org/packages/pakku#comment-902444. I triggered this while trying to build+install pakku on a different computer, then reran it and built successfully.