From: Greg Troxel <gdt@ir.bbn.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: thread assert with 1.8.2
Date: Wed, 22 Aug 2007 19:48:55 -0400 [thread overview]
Message-ID: <rmi3aybb060.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87veb7kxhj.fsf@chbouib.org> ("Ludovic Courtès"'s message of "Thu, 23 Aug 2007 00:36:40 +0200")
I read what Kevin wrote about linux threads, and read your patch again,
and I now agree that it should be checking for the same problem that the
NetBSD pthread ipmlementation errored on.
I ran the tests with pthread debugging turned off:
export PTHREAD_DIAGASSERT=Ae
# ignore errors, log to stdout
During the thread test, I got 69 instances of:
guile: Error detected by libpthread: Unlocking unlocked mutex.
Detected by file "/usr/home/gdt/NetBSD-current/src/lib/libpthread/pthread_mutex.c", line 357, function "pthread_mutex_unlock".
See pthread(3) for information.
and the test passed.
Hope this helps. I do not understand the thread code in guile one
little bit, and short of "grok that and find the bug, either there or in
NetBSD pthread lib", let me know if I can do anything else helpful.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-22 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 0:56 thread assert with 1.8.2 Greg Troxel
2007-08-16 0:35 ` Kevin Ryde
2007-08-22 22:36 ` Ludovic Courtès
2007-08-22 23:39 ` Greg Troxel
2007-08-22 23:48 ` Greg Troxel [this message]
2007-10-02 16:18 ` Ludovic Courtès
2007-10-04 16:22 ` 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=rmi3aybb060.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).