From: Kevin Ryde <user42@zip.com.au>
Cc: Alexey Voinov <voins@voins.program.ru>,
guile-devel <guile-devel@gnu.org>
Subject: Re: segfault in guile 1.6.7
Date: Mon, 23 May 2005 11:34:06 +1000 [thread overview]
Message-ID: <87acmmwws1.fsf@zip.com.au> (raw)
In-Reply-To: <87vf5b2ijr.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 22 May 2005 21:59:36 +0300")
Marius Vollmer <mvo@zagadka.de> writes:
>
> Thanks! I applied it.
I already made a fix (from the head by Han-Wen) in chars.h which
covers this, by stopping signed values getting into the value field of
a char SCM (there's 24 or 56 bits there). Should fix applications
passing "char" to SCM_MAKE_CHAR too.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-05-23 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 17:11 segfault in guile 1.6.7 Alexey Voinov
2005-03-25 20:37 ` Kevin Ryde
2005-03-25 20:47 ` Kevin Ryde
2005-05-22 18:59 ` Marius Vollmer
2005-05-23 1:34 ` Kevin Ryde [this message]
2005-06-06 19:20 ` Marius Vollmer
2005-06-06 22:07 ` Kevin Ryde
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=87acmmwws1.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=voins@voins.program.ru \
/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).