From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/14490] Enable stapdyn in multiarch environments
Date: Thu, 27 Jun 2013 21:32:00 -0000 [thread overview]
Message-ID: <bug-14490-6586-YQ4SdcpTUc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14490-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14490
--- Comment #7 from Josh Stone <jistone at redhat dot com> ---
(In reply to David Smith from comment #6)
> I'm wondering if 32-bit and 64-bit processes can share a pthread mutexes. In
> a 64-bit exe, sizeof(pthread_mutex_t) is 40 bytes. In a 32-bit exe,
> sizeof(pthread_mutex_t) is 24 bytes.
That's a very good point. Gross. I suppose we could create our own locking
primitives, since futex deals in simple ints, but this is definitely a
complication I hadn't thought about.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2013-06-27 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 1:46 [Bug runtime/14490] New: " jistone at redhat dot com
2012-09-07 19:37 ` [Bug dyninst/14490] " jistone at redhat dot com
2013-02-13 3:07 ` fche at redhat dot com
2013-06-07 19:55 ` dsmith at redhat dot com
2013-06-07 20:21 ` jistone at redhat dot com
2013-06-10 14:22 ` dsmith at redhat dot com
2013-06-10 18:05 ` jistone at redhat dot com
2013-06-27 21:10 ` dsmith at redhat dot com
2013-06-27 21:32 ` jistone at redhat dot com [this message]
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=bug-14490-6586-YQ4SdcpTUc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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).