bug#41158: `guix` command segfaults after doing Ctrl-C during a frozen `guix pull`

[zimoun]

Dear,

Thank you for the report.

On Sat, 09 May 2020 at 20:38, JoJo <jo@jo.zone> wrote:
> Due to an unrelated issue, I was updating my system with `guix
> pull`. During update, the process seemed to freeze / get stuck. My
> system was responsive and all, but the `guix pull` output was stuck. I
> don't remember what the last line in the output was, but after
> studying the output of an application of
> `/run/current-system/profile/bin/guix`, I think the output stuck at
> the last step, "building profile with 1 package...". It definitely
> said something about "profile" and "1 package" at least. I don't know
> what caused the freeze. A casual guess is that it's related to my
> screen blanking and the screen locker (`slock`) activatin due to no
> input for a while.

Hum?  Weird…

> Anyways, I decided to end the apparently frozen command, so I killed
> it with Ctrl-C. Immediately afterwards when trying to `guix pull`
> another time, `guix` just started segfaulting. Doesn't matter what
> subcommand I try, or if I call `guix` with no subbcommand -- it just
> segfaults in either case.
>
> ```
> jojo@astoria ~$ guix pull
> Segmentation fault
> jojo@astoria ~$ guix
> Segmentation fault
> jojo@astoria ~$ guix show
> Segmentation fault
> ```

What do these commands

   /run/current-system/profile/bin/guix pull -p ~/.config/guix/current
   guix pull

do?
  


All the best,
simon