bug#33216: using custom optimization options eats goops object

Hi! When running `step.scm' (attached) the expected behaviour is exit 0. Using auto compilation or default optimization options, that's what happens --8<---cut here---start->8--- $ rm -f step.go && guile -e '(step)' step.scm 15:39:41 janneke@dundal:~/src/bug-

bug#33216: using custom optimization options eats goops object

Jan Nieuwenhuizen writes: I get the same with latest stable-2.2 commit d9af6706e8a1a0148d492b222758e49e03d225b7 -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com