From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: Guile fails tests on Tru64 4.0F
Date: Mon, 25 Mar 2002 17:30:45 -0800 [thread overview]
Message-ID: <E16pfnR-0000Jt-00@giblet> (raw)
In-Reply-To: <15494.11847.220704.947920@gargle.gargle.HOWL> (message from David C Sterratt on Wed, 6 Mar 2002 14:57:11 +0000)
From: David C Sterratt <david.c.sterratt@ed.ac.uk>
Date: Wed, 6 Mar 2002 14:57:11 +0000
In libguile/scmconfig.h I see:
/* Define if the system has the type `uintptr_t'. */
/* #undef HAVE_UINTPTR_T */
I can't find any references to SIZEOF_UINTPTR_T, UINTPTR_MAX,
INTPTR_MAX and INTPTR_MIN
this tells me the fundamental type SCM is implemented by "unsigned
long". i suspect there is a bug in srfi-4.c function `make_uvec'.
could you:
- make sure you have relatively recent guile-1.5.x (1.5.6 is fine)
- rerun autogen.sh (if necessary), configure, and make
- do "make install" somewhere (e.g., /tmp)
- save the following to bug-1000.scm:
(use-modules (srfi srfi-4))
(display (u8vector))
- run /tmp/bin/guile under gdb w/ command line: guile -s bug-1000.scm
- set breakpoint at make_uvec and step through it
- report your observations
(see HACKING for some commands for your .gdbinit useful for displaying
SCM values.)
alternatively you can send me hardware to play w/ (haha just kidding).
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next parent reply other threads:[~2002-03-26 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16hxAM-0006IY-00@giblet>
[not found] ` <15492.47715.734375.453398@gargle.gargle.HOWL>
[not found] ` <E16iP7P-0007Km-00@giblet>
[not found] ` <15494.11847.220704.947920@gargle.gargle.HOWL>
2002-03-26 1:30 ` Thien-Thi Nguyen [this message]
2002-04-05 11:55 ` Guile fails tests on Tru64 4.0F David C Sterratt
2002-04-06 2:31 ` Thien-Thi Nguyen
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=E16pfnR-0000Jt-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--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).