From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Whatson <whatson@gmail.com>
Cc: 57948@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.
Date: Wed, 12 Oct 2022 22:34:24 +0200 [thread overview]
Message-ID: <87czawvl0v.fsf__20506.4195835561$1665606935$gmane$org@gnu.org> (raw)
In-Reply-To: <20220922135358.22139-1-whatson@gmail.com> (Andrew Whatson's message of "Thu, 22 Sep 2022 23:53:59 +1000")
Hi Andrew,
Andrew Whatson <whatson@gmail.com> skribis:
> Workaround for <https://bugs.gnu.org/57948>.
>
> * module/system/vm/frame.scm (frame-call-representation): Treat a
> binding as "unspecified" if its slot exceeds 'frame-num-locals'.
Yay, great to see that fixed (or almost)!
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?
Thanks,
Ludo’.
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>.
next parent reply other threads:[~2022-10-12 20:34 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 ` Ludovic Courtès [this message]
[not found] ` <87czawvl0v.fsf@gnu.org>
2022-10-13 3:36 ` bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace 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
[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='87czawvl0v.fsf__20506.4195835561$1665606935$gmane$org@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).