From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: bug with read-string!/partial
Date: Wed, 07 Dec 2005 00:14:14 +0200 [thread overview]
Message-ID: <87ek4p50w9.fsf@zagadka.de> (raw)
In-Reply-To: <430A401D.2060000@xs4all.nl> (Han-Wen Nienhuys's message of "Mon, 22 Aug 2005 23:14:05 +0200")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> Hi,
>
> what's the proper way to use read-string!/partial ?
>
> If I read a file with fewer bytes than the arg of read-string!/partial,
> I get problems down the line [with scm_to_locale_stringn]
Do you pass the right length to scm_to_locale_stringn, i.e, the return
value of read-string!/partial?
Also, maybe there really are #\nul characters in the file and the
error message from scm_to_locale_stringn is entirely deserved.
> In addition, I this error message isn't printed properly, but I get
>
> Converting to PNG...throw from within critical section.
> Geannuleerd
> muurbloem:~/src/lilypond$
This message means that SCM_CRITICAL_SECTION_START/END is used
improperly. There are likely some improper uses in Guile itself (and
this issue is what is holding off the 1.8 release at the moment...),
so it would be good to know exactly what instance of
SCM_CRITICAL_SECTION_START/END is responsible for your abort.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-12-06 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:14 bug with read-string!/partial Han-Wen Nienhuys
2005-08-22 21:17 ` Han-Wen Nienhuys
2005-08-23 0:31 ` Kevin Ryde
2005-08-23 0:34 ` Kevin Ryde
2005-12-06 22:14 ` Marius Vollmer [this message]
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=87ek4p50w9.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).