From: Neil Jerram <neil@ossau.uklinux.net>
To: Stanislav Ievlev <stanislav.ievlev@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Strange deadlocks in guile
Date: Thu, 12 Mar 2009 20:37:39 +0000 [thread overview]
Message-ID: <87eix2wk8c.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <c5318fd90903120152q6f8e47falb77bb8f82c6579d@mail.gmail.com> (Stanislav Ievlev's message of "Thu\, 12 Mar 2009 11\:52\:26 +0300")
Stanislav Ievlev <stanislav.ievlev@gmail.com> writes:
> Greetings!
>
> On my 2.6.18 kernel guile (latest snapshot from git, branch-release-1.8 head)
> in some situations (unfortunately I can't made a testcase) stops forever. Guile
> with 2.6.27 kernel works well.
>
> Strace:
> futex(0xc571890, FUTEX_WAIT, 2, NULL...
>
> Backtrace:
> --
> #0 0x00002b4ba31b4004 in __lll_lock_wait () from /lib64/libpthread.so.0
> #1 0x00002b4ba31af944 in _L_lock_55 () from /lib64/libpthread.so.0
> #2 0x00002b4ba31af341 in pthread_mutex_lock () from /lib64/libpthread.so.0
> #3 0x00002b4ba22f87dc in scm_i_thread_put_to_sleep () from /usr/lib64/
> libguile.so.17
> #4 0x00002b4ba22abfd9 in scm_i_gc () from /usr/lib64/libguile.so.17
> #5 0x00002b4ba22ac338 in scm_gc_for_newcell () from /usr/lib64/libguile.so.17
> #6 0x00002b4ba22cc86f in scm_cons () from /usr/lib64/libguile.so.17
> --
>
> How can I debug and solve this problem?
The backtrace above only has 7 frames, and there should be many more.
Can you get the full backtrace, and also backtraces of all the other
threads?
We've recently been working quite a bit on deadlocks, so I'd say
there's a good chance we'll be able to understand and fix this.
Thanks,
Neil
next prev parent reply other threads:[~2009-03-12 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 8:52 Strange deadlocks in guile Stanislav Ievlev
2009-03-12 20:37 ` Neil Jerram [this message]
2009-03-13 8:36 ` Stanislav Ievlev
2009-03-13 9:22 ` Ludovic Courtès
2009-03-14 11:40 ` Neil Jerram
2009-03-16 7:16 ` Stanislav Ievlev
2009-03-16 7:18 ` Stanislav Ievlev
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=87eix2wk8c.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=stanislav.ievlev@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).