unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen <hanwen@cs.uu.nl>
Cc: jantien@xs4all.nl, guile-devel@gnu.org
Subject: Re: any news on 1.6 yet?
Date: Tue, 2 Jul 2002 02:10:59 +0200	[thread overview]
Message-ID: <15648.61331.590080.201030@blauw.xs4all.nl> (raw)
In-Reply-To: <87fzz3b003.fsf@raven.i.defaultvalue.org>

rlb@defaultvalue.org writes:
> > Can someone puleaze put in the following remark into the GUILE
> > documentation?
> >
> >
> >   Be warned that the thread library (pthreads) will impose a 512k
> >   limit on the stack size, when compiling GUILE with thread
> >   support. 
> >
> > We spent a _long_ time being flabbergasted at why our program dumped
> > core on perfectly valid data and innocent instructions.
> 
> Wow, that's annoying -- do you know if this is an arch dependency, OS
> dependency, etc?

You're f*cked once you link with libpthreads (I could produce a crash
linking to guile --without-threads and libpthreads). Apparently the
thread package does include some functions to set the stackspace, but
those must be called before a thread is spawned. I know zilch about
threads, so I don't know the details behind this.

We managed to get the stack usage of our functions and GC mark
functions down (which is probably a good idea performance wise), but
it was annoying nevertheless.

-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2002-07-02  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 10:53 any news on 1.6 yet? Han-Wen Nienhuys
2002-07-01 21:40 ` Rob Browning
2002-07-02  0:10   ` Han-Wen [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=15648.61331.590080.201030@blauw.xs4all.nl \
    --to=hanwen@cs.uu.nl \
    --cc=guile-devel@gnu.org \
    --cc=jantien@xs4all.nl \
    /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).