all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "David Arroyo" <david@aqwari.net>
To: help-guix@gnu.org
Subject: How do you debug build-side code?
Date: Sun, 03 Apr 2022 15:54:30 -0400	[thread overview]
Message-ID: <868399f1-2248-4bea-8bd4-8cc921f18840@www.fastmail.com> (raw)

Hello,

I currently use Guix on a foreign distro to define development and build environments. I'm trying to extend guix with types that build an s6[1] supervision tree in the store from a declarative definition. I can then use that to build a guix profile (or a pack) with everything needed for s6-svscan to run and supervise these services.

This is my current attempt:

https://git.sr.ht/~droyo/guix-channel/tree/1ca4a1043c1f38bcc118046fa5ba771cf47393a9/item/aqwari/services/s6.scm
https://git.sr.ht/~droyo/guix-channel/tree/1ca4a1043c1f38bcc118046fa5ba771cf47393a9/item/example/router.scm

However, `guix build -f router.scm` currently fails. The specific error is something about incorrect arguments to "apply". I'm sure I can find it eventually, but this is just one of many errors I've made, and I've had a bear of a time fixing them. I feel like I am in uncharted territory, because the docs I can find all talk about packages, and I'm not trying to build a package. Often the stack traced I get do not include my code at all, so it's hard to tell where my mistake is.

I'd love to hear how others debug errors in the build-side code. Is there any way for me to trace the function calls or even have an interactive debugging session?

David

[1]: https://skarnet.org/software/s6/index.html


             reply	other threads:[~2022-04-03 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 19:54 David Arroyo [this message]
2022-04-04  2:58 ` How do you debug build-side code? David Arroyo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868399f1-2248-4bea-8bd4-8cc921f18840@www.fastmail.com \
    --to=david@aqwari.net \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.