enter debugger on failure

enter debugger on failure

[Ricardo Wurmus]

Hi Guix,

sometimes Guix crashes.  That’s sometimes because of existing bugs
(often in importers) or because I’ve just added something that doesn’t
quite work.

When Guix crashes it prints a backtrace and exits.  Would it be possible
to change that behaviour and instead enter a debug REPL where I could
inspect values and resume after correcting the error?

That would be beautiful!

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: enter debugger on failure

[Ludovic Courtès]

Hi!

Ricardo Wurmus <rekado@elephly.net> skribis:

> sometimes Guix crashes.  That’s sometimes because of existing bugs
> (often in importers) or because I’ve just added something that doesn’t
> quite work.
>
> When Guix crashes it prints a backtrace and exits.  Would it be possible
> to change that behaviour and instead enter a debug REPL where I could
> inspect values and resume after correcting the error?

‘guix system’ has a ‘--on-error’ command-line option that we could
perhaps generalize somewhat.  WDYT?

Now, two comments:

  1. importers are “for developers”, so I’m personally more tolerant if
     they’re rough on the edges ;-)

  2. one can always do:

       ./pre-inst-env guile
       scheme@…> ,use(guix scripts import)
       scheme@…> (guix-import "foo" "bar")
       ;; crash!
       scheme@…>[1] ,bt

Ludo’.

Re: enter debugger on failure

[jgart]

Testing