From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Whatson <whatson@gmail.com>
Cc: guile-devel@gnu.org, 57948@debbugs.gnu.org
Subject: Re: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.
Date: Thu, 13 Oct 2022 15:09:16 +0200 [thread overview]
Message-ID: <87fsfrrhtv.fsf@gnu.org> (raw)
In-Reply-To: <CAPE069eQb3Yg9OdgjBw3tC2c-G2Cbo15rjkdjP=uQgvu_MNjpA@mail.gmail.com> (Andrew Whatson's message of "Thu, 13 Oct 2022 13:36:20 +1000")
Hi,
Andrew Whatson <whatson@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> wrote:
>>
>> It would be great if you could add a simple test case though, so that
>> the bug doesn’t eventually come back to haunt us.
>>
>> Could you send an updated patch?
>
> Ah yes, getting this covered in a test is on my list. I had trouble
> writing a reproducer previously, I think the bug might only occur in a
> nested compilation context (top-level error compiling a dependency
> module), but I'll have another go.
Awesome.
>> PS: BTW, it’ll be great to have more patches from you! :-) To that end,
>> please check out the new Guile copyright policy and let us know what
>> option you’d like to choose:
>> <https://lists.gnu.org/archive/html/guile-devel/2022-10/msg00008.html>.
>
> I have already assigned copyright of my work on Guile to the FSF,
> happy for that to remain.
Oh sorry I had overlooked that, perfect!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-10-13 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 7:23 [PATCH] Avoid 'frame-local-ref' errors when printing backtrace Andrew Whatson
2022-09-21 10:50 ` Maxime Devos
2022-09-22 13:53 ` Andrew Whatson
2022-09-22 15:10 ` Maxime Devos
2022-10-12 20:34 ` Ludovic Courtès
2022-10-13 3:36 ` Andrew Whatson
2022-10-13 13:09 ` Ludovic Courtès [this message]
2023-01-11 5:24 ` Andrew Whatson
2023-01-11 23:03 ` Ludovic Courtès
2023-01-12 2:09 ` Andrew Whatson
2022-11-29 18:06 ` lloda
2022-09-22 13:58 ` Andrew Whatson
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=87fsfrrhtv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57948@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=whatson@gmail.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).