From: Maciej Stachowiak <mjs@noisehavoc.org>
Cc: Maciej Stachowiak <mjs@noisehavoc.org>
Subject: Re: [pthreads] performance test using fib.scm
Date: Wed, 11 Dec 2002 05:48:13 -0800 [thread overview]
Message-ID: <20021211054813.B20646@noisehavoc.org> (raw)
In-Reply-To: <xy7hedlghc9.fsf@nada.kth.se>; from djurfeldt@nada.kth.se on Wed, Dec 11, 2002 at 08:11:50AM +0100
On 11Dec2002 08:11AM (+0100), Mikael Djurfeldt wrote:
> Maciej Stachowiak <mjs@noisehavoc.org> writes:
>
> > On 10Dec2002 10:10PM (+0100), Wolfgang Jaehrling wrote:
> >> malloc() in glibc is thread-save, but not reentrant. Since the
> >> behaviour of realloc() is unlikely to differ from malloc() in this
> >> respect, you most certainly have to protect calls to it with a lock.
> >>
> >
> > Huh? Doesn't malloc do it's own locking when modifying global data
> > structures?
>
> This is what I would have expected.
>
> Can someone please verify that malloc is reentrant?
According to the best info I can find on Google, glibc's malloc can be
called safely from multiple threads but cannot necessarily safely be
called from a signal handler (another possible definition of
re-entrant). A mutex would not help with calling it from a signal
handler anyway, though. So don't bother with locking.
If you truly suspect heap corruption I suggest running with
MALLOC_CHECK_=2 set in your environment. This should detect many kinds
of heap corruption.
Regards,
Maciej
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-12-11 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:16 [pthreads] performance test using fib.scm Mikael Djurfeldt
2002-12-10 21:10 ` Wolfgang Jaehrling
2002-12-10 20:10 ` Mikael Djurfeldt
2002-12-11 20:05 ` Christopher Cramer
2002-12-11 5:02 ` Maciej Stachowiak
2002-12-11 7:11 ` Mikael Djurfeldt
2002-12-11 13:48 ` Maciej Stachowiak [this message]
2002-12-11 23:43 ` Han-Wen Nienhuys
2002-12-11 16:59 ` Wolfgang Jaehrling
[not found] ` <200212110202.gBB22Et27423@mule.m17n.org>
2002-12-11 17:27 ` Wolfgang Jaehrling
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=20021211054813.B20646@noisehavoc.org \
--to=mjs@noisehavoc.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).