From: "joshua dot i dot stone at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2056] Cannot iterate pmaps
Date: Wed, 21 Dec 2005 20:45:00 -0000 [thread overview]
Message-ID: <20051221203729.10015.qmail@sourceware.org> (raw)
In-Reply-To: <20051214214948.2056.hunt@redhat.com>
------- Additional Comments From joshua dot i dot stone at intel dot com 2005-12-21 20:37 -------
(In reply to comment #1)
> Created an attachment (id=809)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=809&action=view)
> enable pmap iteration
The patch allows the testcase to build, but it deadlocks when you run it. The
deadlock is here:
foreach (i in foo)
printf("count of foo[%d] = %d\n", i, @count(foo[i]))
This happens because the 'foreach' opens a readlock on foo, and then '@count'
tries to open a writelock. While this is a valid problem, it may be out of the
scope of this bug.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |joshua dot i dot stone at
| |intel dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2056
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2005-12-21 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 23:32 [Bug translator/2056] New: " hunt at redhat dot com
2005-12-21 20:37 ` [Bug translator/2056] " joshua dot i dot stone at intel dot com
2005-12-21 20:45 ` joshua dot i dot stone at intel dot com [this message]
2005-12-22 1:17 ` fche at redhat dot com
2006-01-04 21:00 ` [Bug translator/2056] avoid locking within foreach iteration for maps & pmaps fche at redhat dot com
2006-01-05 6:08 ` hunt at redhat dot com
2006-01-05 22:08 ` fche at redhat dot com
2006-01-05 22:35 ` hunt at redhat dot com
2006-01-13 3:58 ` joshua dot i dot stone at intel dot com
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051221203729.10015.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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).