unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: Kannan Vijayan <INVALID.NOREPLY@gnu.org>
Cc: bug-guile@gnu.org, Kannan Vijayan <kannan.vij@gmail.com>
Subject: Re: [bug #24554] Pthreads and Stack overflow in guile (reopen bug 20814?) (guile 1.8.5)
Date: Tue, 14 Oct 2008 12:50:44 -0400	[thread overview]
Message-ID: <2635792.1059581224003044911.JavaMail.root@cdptpa-web28-z01> (raw)


---- Kannan Vijayan <INVALID.NOREPLY@gnu.org> wrote: 
> 
> Follow-up Comment #2, bug #24554 (project guile):
> 
> I have confirmed that the bug is not really a bug.  The debian changelog
> indicates that the --with-threads option was turned off with one of the 1.8.0
> releases of guile due to a bug.  It doesn't seem to have been turned back on
> since then.

I would imagine that --with-threads will not be turned back on until a 1.10.x (or 2.0.0 ?) release of Guile.

My limited understanding of the situation (possibly incorrect):  Using --without-threads changes the sizes of some data structures (I'm guessing they are smaller, with some pthreads stuff #ifdef'ed out), so that code compiled for one way will segfault when linked with code compiled for the other way.

As far as just releasing new packages --with-threads, It's just not possible to go back an recompile all the currently existing packages on already existing systems.

-Dale






             reply	other threads:[~2008-10-14 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 16:50 dsmich [this message]
2008-10-14 21:48 ` [bug #24554] Pthreads and Stack overflow in guile (reopen bug 20814?) (guile 1.8.5) Neil Jerram
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15 18:43 dsmich
2008-10-14  1:39 Kannan Vijayan
2008-10-14  3:05 ` Kannan Vijayan
2008-10-14  8:53   ` Neil Jerram
2008-10-14 15:07   ` Kannan Vijayan
2008-11-30 18:42     ` Ludovic Courtès
2009-07-20 21:51       ` Ludovic Courtès

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=2635792.1059581224003044911.JavaMail.root@cdptpa-web28-z01 \
    --to=dsmich@roadrunner.com \
    --cc=INVALID.NOREPLY@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=kannan.vij@gmail.com \
    /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).