From: Maxime Devos <maximedevos@telenet.be>
To: 50153@debbugs.gnu.org, 39954@debbugs.gnu.org
Subject: bug#39954: bug#50153: Acknowledgement (call-with-values outside tail position + backtrace + compilation causes segfault)
Date: Sat, 21 Aug 2021 22:17:56 +0200 [thread overview]
Message-ID: <1d57f669b5c2cf2ae13c68e6cd267bf107553e94.camel@telenet.be> (raw)
In-Reply-To: <handler.50153.B.16295696024250.ack@debbugs.gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]
I did some debugging on the C side, using 'rr':
LD_LIBRARY_PATH=.libs ../meta/uninstalled-env rr record ./.libs/guile --fresh-auto-compile -l ../crash.scm
it leads to a segfault, as expected. According to #39954, which looks
similar, 'frame-local-ref' returns (SCM)0x0. So I tried some reverse debugging:
rr replay guile-3
break scm_frame_local_ref
reverse-continue
reverse-continue
I noticed "repr" was STACK_ITEM_SCM, and item->as_scm was set to 0x07
(which is invalid). On another run, it was set to 0x09 (also invalid?).
I modified scm_frame_local_ref a bit so it ignores these 0x07 and 0x09
and treats them like SCM_EOF_VAL instead. That allows printing the backtrace,
though I don't see those #<eof> appearing in the output.
Would someone know what's going on here?
Greetings,
Maxime
[-- Attachment #1.2: printf.patch --]
[-- Type: text/x-patch, Size: 781 bytes --]
diff --git a/libguile/frames.c b/libguile/frames.c
index 0bb40579c..87afaec3d 100644
--- a/libguile/frames.c
+++ b/libguile/frames.c
@@ -41,6 +41,7 @@
#include "frames.h"
+#include <stdio.h>
SCM
scm_c_make_frame (enum scm_vm_frame_kind kind, const struct scm_frame *frame)
@@ -272,6 +273,11 @@ scm_frame_local_ref (SCM frame, SCM index, SCM representation)
switch (repr)
{
case STACK_ITEM_SCM:
+ fprintf(stderr, "i: %u SCM: %p\n", (unsigned) i, (void*)item->as_u64);
+ if (item->as_u64 == 0x07)
+ return SCM_EOF_VAL;
+ if (item->as_u64 == 0x09)
+ return SCM_EOF_VAL;
return item->as_scm;
case STACK_ITEM_F64:
return scm_from_double (item->as_f64);
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2021-08-21 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 18:13 bug#50153: call-with-values outside tail position + backtrace + compilation causes segfault Maxime Devos
[not found] ` <handler.50153.B.16295696024250.ack@debbugs.gnu.org>
2021-08-21 18:30 ` bug#39954: bug#50153: Acknowledgement (call-with-values outside tail position + backtrace + compilation causes segfault) Maxime Devos
2021-08-21 20:17 ` Maxime Devos [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=1d57f669b5c2cf2ae13c68e6cd267bf107553e94.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=39954@debbugs.gnu.org \
--cc=50153@debbugs.gnu.org \
/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).