From: "Dylan Nicholson" <dylannic@bigpond.net.au>
Cc: guile-user@gnu.org
Subject: Re: libguile on Windows
Date: Tue, 11 Oct 2005 08:52:02 +1000 [thread overview]
Message-ID: <00b001c5cded$3aede6a0$6b01a8c0@DORIAN> (raw)
Sorry for the top-post, but now I'm pretty sure I know what the problem is.
I wasn't sure how to create the .x files, so I simply created them all as
blank files!
Obviously this isn't right, so if anyone can send me the .x files, or simple
instructions on how to create them *without* any GNU tools, that would be
great.
----- Original Message -----
From: "Dylan Nicholson" <dylannic@bigpond.net.au>
To: "Neil Jerram" <neil@ossau.uklinux.net>
Cc: <guile-user@gnu.org>
Sent: Tuesday, October 11, 2005 8:38 AM
Subject: Re: libguile on Windows
>> ----- Original Message -----
>> From: "Neil Jerram" <neil@ossau.uklinux.net>
>>>
>>> Can you hack the code somehow so that the debug and backtrace options
>>> are set:
>>>
>>> SCM_DEVAL_P = 1;
>>> SCM_BACKTRACE_P = 1;
>>> SCM_RESET_DEBUG_MODE;
>>>
>>> (This would have to be after the init functions for debug.c.)
>>
>> I just get
>>
>> Backtrace:
>> In unknown file:
>> ?: 0*
>>
>> Then an access violation trying to access a null pointer in unmemocopy
>> (eval.c, line 1291). unmemocopy calls itself recursively using
>> SCM_CAR( ), and at some point SCM_CAR returns 0, which unmemocopy can't
>> handle.
>>
>> This happens no matter where I put the code (e.g. before callling
>> scm_boot_guile or just before scm_load_startup_files())
>>
> Ok, I added an extra test to unmemocopy (to test that the argument is
> null), and now I get
>
> Backtrace:
> In unknown file:
> ?: 0* (define begin-deprecated (procedure->memoizing-macro (lambda #
> #)))
>
> <unnamed port>: In expression (define begin-deprecated
> (procedure->memoizing-macro #)):
> <unnamed port>: Unbound variable: define
>
>
> Hope that means more to you than it does to me! I don't understand why I
> needed to
> change unmemocopy though.
>
>
>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2005-10-10 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 22:52 Dylan Nicholson [this message]
2005-10-10 23:09 ` libguile on Windows Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2005-10-10 23:43 Dylan Nicholson
2005-10-10 23:23 Dylan Nicholson
2005-10-10 23:40 ` Neil Jerram
[not found] ` <00e301c5cdf5$02aa3d40$6b01a8c0@DORIAN>
2005-10-11 22:37 ` Neil Jerram
2005-10-10 22:38 Dylan Nicholson
[not found] <001f01c5ca06$9a957db0$6401a8c0@DORIAN>
[not found] ` <87vf07afac.fsf@ossau.uklinux.net>
2005-10-09 21:53 ` Dylan Nicholson
2005-10-10 16:47 ` Neil Jerram
2005-10-10 22:19 ` Dylan Nicholson
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='00b001c5cded$3aede6a0$6b01a8c0@DORIAN' \
--to=dylannic@bigpond.net.au \
--cc=guile-user@gnu.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).