From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org, johns776@pilot.msu.edu
Subject: Re: Fix for 1001-local-eval-error-backtrace-segfaults - please review
Date: Thu, 02 May 2002 20:50:17 -0700 [thread overview]
Message-ID: <E173U5J-0004uh-00@giblet> (raw)
In-Reply-To: <m3k7qmhfj9.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 02 May 2002 13:59:06 +0100)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: 02 May 2002 13:59:06 +0100
- SCM_SETCAR (SCM_CAR (env), scm_cons (n, SCM_CAR (SCM_CAR (env))));
The copy in scm_unmemocopy, which looks as though it might be
intended to fix this problem [...]
was this used previously? (i'm trying to crawl inside the head of
whoever wrote it this way in the first place.)
Fix isn't very elegant, though;
is there a nicer way of doing this?
both the old way and the new way involve mutating some nested list
structure, so i'm guessing that doesn't play into "elegance". i'm
wondering what is it about this fix that makes it not very elegant?
2. Rerun of problem scenarios:
cool. this touches upon the need to extend the testing framework to
handle interactive cases. actually, i believe that's already possible
w/ the current framework via (ice-9 expect); the limitation really is
that all tests share an execution environment -- this is fine for the
most part, but undesirable for this kind of bug.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-05-03 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 12:59 Fix for 1001-local-eval-error-backtrace-segfaults - please review Neil Jerram
2002-05-03 3:50 ` Thien-Thi Nguyen [this message]
2002-05-05 14:00 ` Neil Jerram
2002-05-15 12:43 ` Thien-Thi Nguyen
2002-05-18 13:47 ` Neil Jerram
2002-05-07 18:36 ` Marius Vollmer
2002-05-07 19:30 ` Neil Jerram
2002-05-07 19:39 ` Marius Vollmer
2002-05-11 15:52 ` Neil Jerram
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=E173U5J-0004uh-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=johns776@pilot.msu.edu \
--cc=ttn@glug.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).