From: Neil Jerram <neil@ossau.uklinux.net>
To: Fabian Schuetz <info@fms-edv.de>
Cc: bug-guile@gnu.org
Subject: Re: Segmentation Fault in guile-1.8.7 on recent Macbook Pro
Date: Sat, 30 Oct 2010 16:58:45 +0100 [thread overview]
Message-ID: <87ocaboacn.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <20101023114021.GA18953@eris.fms-edv.de> (Fabian Schuetz's message of "Sat, 23 Oct 2010 13:40:21 +0200")
Fabian Schuetz <info@fms-edv.de> writes:
> While experimenting with "undefine", I discovered, that
> even quite important functions, like "write" or "display"
> can be undefined. The problem is, that calling them
> after they have been "undefined", leads to an
> endless regression, displaying a Segmentation fault,
> when finally interrupted.
>
> If I "undefine" list:
> (undefine list)
> and call it afterwards:
> (list 1 2 3 4)
> I get the expected "ABORT: (unbound-variable)
>
> I would be glad to help out, to fix this.
Can you explain why you need to undefine those functions?
Unless there's a compelling need, I'm afraid it's unlikely anyone will
work on this, because most developer focus is now on 1.9/2.0.
Thanks,
Neil
next prev parent reply other threads:[~2010-10-30 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 11:40 Segmentation Fault in guile-1.8.7 on recent Macbook Pro Fabian Schuetz
2010-10-30 15:58 ` Neil Jerram [this message]
2010-11-18 15:10 ` Andy Wingo
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=87ocaboacn.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=info@fms-edv.de \
/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).