From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 41581@debbugs.gnu.org
Subject: bug#41581: Redirecting ‘guix graph’ to bcachefs file causes backtrace(?)
Date: Thu, 28 May 2020 20:53:30 +0200 [thread overview]
Message-ID: <87tuzz3n85.fsf@nckx> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 255 bytes --]
Guix,
Redirecting guix's output to a file on a bcachefs file system
triggers a backtrace.
Of course I don't expect anyone else to be doing this, but does
anyone have a clue as to what *could* be happening? Redirection
to a file in /tmp works fine.
[-- Attachment #1.2: Type: text/plain, Size: 998 bytes --]
λ findmnt /
TARGET SOURCE FSTYPE OPTIONS
/ /dev/sda1 bcachefs
rw,relatime,compression=lz4,gc_reserve_percent=5,discard
λ guix --help > ~/halpy
Backtrace:
11 (primitive-load
"/home/nckx/.config/guix/current/bin/guix")
In ice-9/eval.scm:
293:34 10 (_ #<directory (guile-user) 705f90896f00>)
196:35 9 (_ #<directory (guile-user) 705f90896f00>)
In ice-9/boot-9.scm:
3297:17 8 (resolve-interface (guix ui) #:select _ #:hide _
#:prefix _ #:renamer _ #:version _)
In ice-9/threads.scm:
390:8 7 (_ _)
In ice-9/boot-9.scm:
3223:13 6 (_)
In ice-9/threads.scm:
390:8 5 (_ _)
In ice-9/boot-9.scm:
3507:20 4 (_)
2806:4 3 (save-module-excursion _)
3527:26 2 (_)
In unknown file:
1 (primitive-load-path "guix/ui" #<procedure
705f90ca97e0 at ice-9/boot-9.scm:3514:37 ()>)
In guix/ui.scm:
1328:19 0 (_)
guix/ui.scm:1328:19: In procedure terminal-window-size: Operation
not permitted
[-- Attachment #1.3: Type: text/plain, Size: 22 bytes --]
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2020-05-28 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 18:53 Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-05-29 16:36 ` bug#41581: Redirecting ‘guix graph’ to bcachefs file causes backtrace(?) Ludovic Courtès
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=87tuzz3n85.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=41581@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).