From: James Bergstra <james.bergstra@umontreal.ca>
Cc: bug-guile@gnu.org, James Bergstra <james.bergstra@umontreal.ca>
Subject: Re: simple-format causes segfault?
Date: Sun, 7 May 2006 14:15:19 -0400 [thread overview]
Message-ID: <20060507181518.GB9700@aphex.iro.umontreal.ca> (raw)
In-Reply-To: <877j4yrb8y.fsf@ossau.uklinux.net>
> To begin with, please just post the code and any input that it needs
> to repro the problem. That should be enough if the problem is not
> specific to your environment. If it isn't enough, we can move onto
> cores later.
Thank you for your reply. Unfortunately, my program is not easy to send. I've
spent an hour just now trying to distill a simple test case with no luck. Almost
any change I make to the program seems to cause it not to segfault. For
example:
- replacing an open file with current-input-port
- moving the script to a different folder (perhaps to a sufficiently short path?)
- moving code from a (load)'ed file into the script itself
One bit of evidence to maybe keep in mind as you continue to improve guile is
that sometimes it ran perfectly, sometimes it segfaulted, and sometimes it
aborted with this message:
ERROR: In procedure simple-format:
ERROR: Wrong type argument in position 1: #<freed cell 0x2aaaaae44cb0; GC missed
a reference>
I was very surprised that some of these actions had an effect on the behaviour
of my script. Since this problem has such a simple workaround (use display
instead of simple-format), I don't want to explore these mysteries any longer.
I'm baffled and I'm giving up :(
I've posted the cores on my website:
http://www-etud.iro.umontreal.ca/~bergstrj/guile-cores/
--
James Bergstra
http://www-etud.iro.umontreal.ca/~bergstrj
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-05-07 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 3:38 simple-format causes segfault? James Bergstra
2006-05-06 22:39 ` Marius Vollmer
2006-05-06 23:20 ` Neil Jerram
2006-05-07 18:15 ` James Bergstra [this message]
2006-05-07 23:12 ` Kevin Ryde
2006-05-09 0:58 ` Rob Browning
2006-05-09 2:35 ` Rob Browning
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=20060507181518.GB9700@aphex.iro.umontreal.ca \
--to=james.bergstra@umontreal.ca \
--cc=bug-guile@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).