From: "Ludovic Courtès" <ludo@gnu.org>
To: 38388@debbugs.gnu.org, Andy Wingo <wingo@igalia.com>
Subject: bug#38388: [2.9.5] Inaccurate source location info for unbound variables
Date: Sat, 07 Mar 2020 17:06:56 +0100 [thread overview]
Message-ID: <8736aki1y7.fsf@gnu.org> (raw)
In-Reply-To: <8736ea64vg.fsf@inria.fr> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Tue, 26 Nov 2019 16:20:51 +0100")
Hi,
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
> I have a test that runs ‘guix system build’ on this file:
>
> (use-modules (gnu)) ; 1
> (use-service-modules networking) ; 2
>
> (operating-system ; 4
> (host-name "antelope") ; 5
> (timezone "Europe/Paris") ; 6
> (locale "en_US.UTF-8") ; 7
>
> (bootloader (GRUB-config (target "/dev/sdX"))) ; 9
> (file-systems (cons (file-system
> (device (file-system-label "root"))
> (mount-point "/")
> (type "ext4"))
> %base-file-systems)))
>
> Here, ‘GRUB-config’ is unbound, and the test expects to see a stack
> frame corresponding to line 9.
>
> However, the stack frame we get is for line 11, char 32, which
> corresponds to (file-system-label "root").
I can’t say I got to the bottom of why we got this weird line number,
but commit d3a775ff10cbd0e14af38d6f900a7538db89bd90 solves this specific
issue.
Ludo’.
prev parent reply other threads:[~2020-03-07 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:20 bug#38388: [2.9.5] Inaccurate source location info for unbound variables Ludovic Courtès
2019-11-27 9:53 ` Andy Wingo
2019-11-28 8:20 ` Ludovic Courtès
2019-11-29 11:04 ` Andy Wingo
2020-03-07 16:06 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736aki1y7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38388@debbugs.gnu.org \
--cc=wingo@igalia.com \
/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.
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).