all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Debugging and source code
Date: Mon, 30 Jan 2017 11:08:23 +0100	[thread overview]
Message-ID: <20170130110823.57c309f5@scratchpost.org> (raw)
In-Reply-To: <878tpshq8i.fsf@gnu.org>

Hi,

for example when you try 

  guix build -S ldc

it will not put phobos in the correct place (which is unpacked to the correct place in a phase).

It would be nice if there was a way to run gdb after the build phase ran.

[I guess easiest would be if one could insert something after the 'build phase (and/or after the 'unpack phase) from the command line. Sounds hacky, though.
 Or maybe a phase that's always there in the build systems which doesn't do anything if no command line "enable" flag is given. That sounds hacky.]

Or maybe something like --keep-failed just that it always keeps (also when not failed). Huh, that would go a long way. What would you think about that?

  reply	other threads:[~2017-01-30 10:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  6:53 Debugging and source code Pjotr Prins
2017-01-25 13:22 ` Ludovic Courtès
2017-01-25 13:26   ` Pjotr Prins
2017-01-25 17:54     ` Ludovic Courtès
2017-01-26  3:58       ` Pjotr Prins
2017-01-26  8:11         ` Chris Marusich
2017-01-26  8:43           ` Pjotr Prins
2017-01-26  8:58           ` Tobias Geerinckx-Rice
2017-01-26 18:03             ` Ludovic Courtès
2017-01-26  9:54         ` Ludovic Courtès
2017-01-28  4:57           ` Pjotr Prins
2017-01-30  9:05             ` Ludovic Courtès
2017-01-30 10:08               ` Danny Milosavljevic [this message]
2017-01-25 20:41   ` Danny Milosavljevic
2017-01-26  4:03     ` Pjotr Prins

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=20170130110823.57c309f5@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.