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: Wed, 15 May 2002 05:43:27 -0700 [thread overview]
Message-ID: <E177y7r-0000bs-00@giblet> (raw)
In-Reply-To: <m3it62elt0.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 05 May 2002 15:00:59 +0100)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: 05 May 2002 15:00:59 +0100
No; the new way doesn't mutate at all. It creates a new environment
that shares some substructure with the old environment.
ok i see this now.
But, does this test need a different execution environment? It's true
for any existing test case that, if it causes a SEGV, the following
test cases won't run. This doesn't worry us much because SEGVs aren't
an important part of our plans :-)
sorry, "different" was unclear. it needs to have an independent
execution environment, which may be the same in construction as for the
other tests, for precisely the reason you give.
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-15 12:43 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
2002-05-05 14:00 ` Neil Jerram
2002-05-15 12:43 ` Thien-Thi Nguyen [this message]
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=E177y7r-0000bs-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).