unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: guile-devel@gnu.org
Subject: possible hash deadlock with recent changes
Date: Sat, 7 May 2011 10:58:03 -0400	[thread overview]
Message-ID: <20110507145803.DOWDN.34939.root@cdptpa-web21-z02> (raw)

Recent changes to stable-2.0 seem to cause a deadlock in scwm.  Here is the last 10 frames of a backtrace.

-Dale

(gdb) bt
#0  0xb77fa424 in __kernel_vsyscall ()
#1  0xb734cf02 in __lll_lock_wait ()
    at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:142
#2  0xb734839b in _L_lock_728 () from /lib/i686/cmov/libpthread.so.0
#3  0xb73481c1 in __pthread_mutex_lock (mutex=0xb74e60a0)
    at pthread_mutex_lock.c:61
#4  0xb74d4737 in GC_lock () at pthread_support.c:1681
#5  0xb74c8b79 in GC_general_register_disappearing_link (link=0x8882e14, 
    obj=0x886be50) at finalize.c:156
#6  0xb75716eb in set_weak_cdr (data=0xbf9f5b18) at hashtab.c:783
#7  0xb74c74dc in GC_call_with_alloc_lock (fn=0xb75716a0 <set_weak_cdr>, 
    client_data=0xbf9f5b18) at finalize.c:925
#8  0xb7572b30 in scm_hash_fn_set_x (table=0x885f3f0, obj=0x89f2a30, 
    val=0x886be50, hash_fn=0xb7571050 <scm_ihash>, 
    assoc_fn=0xb7539820 <scm_sloppy_assoc>, closure=0x0) at hashtab.c:808
#9  0xb7572be7 in scm_hash_set_x (table=0x885f3f0, key=0x89f2a30, 
    val=0x886be50) at hashtab.c:1108
#10 0x080659c4 in ScmMakeColor (cn=0xbf9f5bf1 "rgb:5f5f/5f5f/5f5f", 
    perror_status=0x0) at color.c:230




             reply	other threads:[~2011-05-07 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07 14:58 dsmich [this message]
2011-05-08 14:34 ` possible hash deadlock with recent changes Ludovic Courtès
2011-05-08 18:43   ` dsmich
2011-05-25 16:52     ` dsmich
2011-07-01 10:31   ` Andy Wingo
2011-06-16 12:30 ` Andy Wingo
2011-06-16 14:02   ` dsmich

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=20110507145803.DOWDN.34939.root@cdptpa-web21-z02 \
    --to=dsmich@roadrunner.com \
    --cc=guile-devel@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).