From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Whatson <whatson@gmail.com>
Cc: lloda <lloda@sarc.name>, 57948-done@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.
Date: Thu, 12 Jan 2023 00:03:22 +0100 [thread overview]
Message-ID: <87sfggishx.fsf__42968.7126934127$1673478275$gmane$org@gnu.org> (raw)
In-Reply-To: <CAPE069deSOMm8ZoDRd_opj46Rn_0UX3T0uhRUw0xL71QPQsWWg@mail.gmail.com> (Andrew Whatson's message of "Wed, 11 Jan 2023 15:24:15 +1000")
Hi,
Andrew Whatson <whatson@gmail.com> skribis:
> commit 164bdce6acf53796cb96ef1930a89c6caf84bc39
> Author: Andrew Whatson <whatson@gmail.com>
> Date: Wed Jan 11 14:04:32 2023 +1000
>
> Test for 'frame-local-ref' errors when printing backtrace.
>
> This test reproduces the error from <https://bugs.gnu.org/56493>, and
> passes with the workaround which was merged in commit
> c7fa78fc751eb336bcfafbb5ac59c460ee2c5d7a.
>
> * test-suite/tests/eval.test ("avoid frame-local-ref out of range"): New
> test.
Applied, thanks!
Ludo’.
PS: Please use ‘git format-patch’ so the patch can be directly consumed
by ‘git am’.
next prev parent reply other threads:[~2023-01-11 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56d1283b-ac09-8f62-8657-de99578e1a6c@telenet.be>
[not found] ` <20220922135358.22139-1-whatson@gmail.com>
2022-10-12 20:34 ` bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace Ludovic Courtès
[not found] ` <87czawvl0v.fsf@gnu.org>
2022-10-13 3:36 ` Andrew Whatson
[not found] ` <CAPE069eQb3Yg9OdgjBw3tC2c-G2Cbo15rjkdjP=uQgvu_MNjpA@mail.gmail.com>
2022-10-13 13:09 ` Ludovic Courtès
2023-01-11 5:24 ` Andrew Whatson
[not found] ` <CAPE069deSOMm8ZoDRd_opj46Rn_0UX3T0uhRUw0xL71QPQsWWg@mail.gmail.com>
2023-01-11 23:03 ` Ludovic Courtès [this message]
[not found] ` <87sfggishx.fsf@gnu.org>
2023-01-12 2:09 ` 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='87sfggishx.fsf__42968.7126934127$1673478275$gmane$org@gnu.org' \
--to=ludo@gnu.org \
--cc=57948-done@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=lloda@sarc.name \
--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).