From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Latest guile 1.9 segfault in GC
Date: Wed, 18 Aug 2010 16:12:29 +0200 [thread overview]
Message-ID: <87lj84m2lu.fsf@gnu.org> (raw)
In-Reply-To: 20100817140858.GA13359@securactive.net
Hi,
Cedric Cellier <rixed@happyleptic.org> writes:
> But finaly, thanks to libgc's debug message, I got it.
> Actually, libgc overwrite pthread_create (and pthread_sigmask,
> and a few more) to know when a new thread is started.
> But this overloading is done "softly", ie. by a define in a
> C header file.
[...]
> So, in conclusion : always include libguile.h in the compilation
> units calling pthread functions.
That’s not entirely true, see Section “Thread Support” at
<http://www.hpl.hp.com/personal/Hans_Boehm/gc/gcdescr.html>:
All implementations must intercept thread creation and a few other
thread-specific calls to allow enumeration of threads and location of
thread stacks. This is current accomplished with # define's in gc.h
(really gc_pthread_redirects.h), or optionally by using ld's function
call wrapping mechanism under Linux.
Indeed, here’s what I have on GNU/Linux:
$ objdump -T ~/soft/lib/libgc.so|grep pthread_create
000000000001ef80 g DF .text 000000000000028e Base GC_pthread_create
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.2.5 pthread_create
What OS do you use?
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-08-18 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 9:09 Latest guile 1.9 segfault in GC Cedric Cellier
2010-08-17 13:08 ` Cedric Cellier
2010-08-18 14:07 ` Ludovic Courtès
2010-08-17 14:08 ` Cedric Cellier
2010-08-18 14:12 ` Ludovic Courtès [this message]
2010-08-18 16:16 ` Andy Wingo
2010-08-21 1:42 ` rixed
2010-08-23 12:47 ` Cedric Cellier
2010-08-24 16:31 ` 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=87lj84m2lu.fsf@gnu.org \
--to=ludo@gnu.org \
--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).