From: Maxime Devos <maximedevos@telenet.be>
To: Girish <girishm@posteo.net>
Cc: 53369@debbugs.gnu.org
Subject: bug#53369: guix pull command fails on a torified bash shell
Date: Fri, 21 Jan 2022 10:49:03 +0100 [thread overview]
Message-ID: <9c5f0f9eea5f2adb56c16ed0f86d98816fd1e563.camel@telenet.be> (raw)
In-Reply-To: <c3e3e09b-f194-73eb-1a1d-6ec7ee1b49b3@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]
[Please keep debbugs in CC or To]
> guix pull command fails on a torified bash shell
Does it also happen outside a torified shell?
torify sets LD_PRELOAD, which is rather fragile ...
E.g., if torify comes from a foreign distro and guix comes from guix,
then quite possibly there's some kind of binary incompatibility in-
between.
Anyway, torify probably doesn't do what you want it to do, because the
substitutes and most source code is downloaded through the guix daemon,
which is probably not torified. I recommend setting the 'http_proxy'
and 'https_proxy' environment variables instead (for the daemon and
user), although there might be some situations in which they are not
respected.
Girish schreef op vr 21-01-2022 om 08:54 [+0000]:
> Actually, it prints 'Segmentation fault' when I run `guix pull`.
Maybe look in 'dmesg' to see if there was an out-of-memory situation.
> When I run `/run/current-system/profile/bin/guix pull` it runs fine
> but ends with following exception:
> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
> In procedure scm_lreadr: #<unknown port>:16:144: Unknown # object #\<
> I'm not sure whether the above details are enough.
> How can I view the complete backtrace for `guix`?
Normally, the backtrace is printed automatically, looking like
something along these lines:
> Backtrace:
> In ice-9/boot-9.scm:
> 1752:10 6 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
> 5 (apply-smob/0 #<thunk 7f1cc976d080>)
> In ice-9/boot-9.scm:
> 724:2 4 (call-with-prompt _ _ #<procedure default-prompt-
> handle…>)
> In ice-9/eval.scm:
> 619:8 3 (_ #(#(#<directory (guile-user) 7f1cc9773c80>)))
> In ice-9/boot-9.scm:
> 2835:4 2 (save-module-excursion _)
> 4380:12 1 (_)
> In $HOME/source-code/rw/guix/q.scm:
> 1:1 0 (_)
>
> $HOME/source-code/rw/guix/q.scm:1:1: Unbound variable: foo
Basically, the backtrace starts at the 'Backtrace:' line.
But it seems like it was not printed in your case ...
Greetings
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-01-21 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 15:47 bug#53369: guix pull command fails on a torified bash shell Girish
2022-01-20 10:04 ` Maxime Devos
[not found] ` <c3e3e09b-f194-73eb-1a1d-6ec7ee1b49b3@posteo.net>
2022-01-21 9:49 ` Maxime Devos [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c5f0f9eea5f2adb56c16ed0f86d98816fd1e563.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53369@debbugs.gnu.org \
--cc=girishm@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).