From: ludo@gnu.org (Ludovic Courtès)
To: Benno Evers <benno@bmevers.de>
Cc: 21767@debbugs.gnu.org
Subject: bug#21767: Matching debug symbol and package versions
Date: Sat, 21 Nov 2015 17:56:56 +0100 [thread overview]
Message-ID: <87mvu770kn.fsf@gnu.org> (raw)
In-Reply-To: <562EB405.30207@bmevers.de> (Benno Evers's message of "Tue, 27 Oct 2015 00:15:17 +0100")
Benno Evers <benno@bmevers.de> skribis:
> assume I have installed some package
>
> /gnu/store/xxx-daemon-1.0
>
> After a while I notice that it's inexplicably hanging, so I do 'guix
> package -i daemon-1.0:debug', attach to the daemon with gdb, and...no
> debug symbols can be loaded! Turns out, in the meantime the hash has
> changed so i installed
>
> /gnu/store/yyy-daemon-1.0:debug
I realized that I quickly focused on the issue without looking at the
more general context.
The “in the meantime” above means that you had run ‘guix pull’ or
similar, thereby making the previous package recipe unavailable and
leaving you unable to install matching debugging symbols.
On my laptop, I typically run ‘guix package -u’ every time I do ‘guix
pull’, so I cannot find myself in a situation where I’m unable to
install debugging symbols of already installed packages.
This is just to say that the scenario described here can indeed happen,
but is probably not that common. And I don’t mean this to be an excuse
to avoid difficult work. ;-)
I think that the solutions I proposed are worse than the problem,
because they’re complex and would depend on external state, thus making
them look non-deterministic.
So I think I’ll punt and mark it as “wontfix.”
Thoughts?
Ludo’.
prev parent reply other threads:[~2015-11-21 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 23:15 bug#21767: Matching debug symbol and package versions Benno Evers
2015-10-27 15:56 ` Ludovic Courtès
2015-10-27 16:40 ` Efraim Flashner
2015-10-27 17:23 ` Ludovic Courtès
2015-11-21 16:56 ` Ludovic Courtès [this message]
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=87mvu770kn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21767@debbugs.gnu.org \
--cc=benno@bmevers.de \
/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.