From: Alan Jones <1808565@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1808565] [NEW] Reading /proc/self/task/<pid>/maps is not remapped to the target
Date: Fri, 14 Dec 2018 17:51:43 -0000 [thread overview]
Message-ID: <154480990326.22999.12064081216456974155.malonedeb@soybean.canonical.com> (raw)
Public bug reported:
Seeing this in qemu-user 3.1.0
The code in is_proc_myself which supports remapping of /proc/self/maps
and /proc/<pid>/maps does not support remapping of
/proc/self/task/<pid>/maps or /proc/<pid>/task/<pid>/maps. Extending
is_proc_myself to cover these cases causes the maps to be rewritten
correctly.
These are useful in multithreaded programs to avoid freezing the entire
program to capture the maps for a single tid.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1808565
Title:
Reading /proc/self/task/<pid>/maps is not remapped to the target
Status in QEMU:
New
Bug description:
Seeing this in qemu-user 3.1.0
The code in is_proc_myself which supports remapping of /proc/self/maps
and /proc/<pid>/maps does not support remapping of
/proc/self/task/<pid>/maps or /proc/<pid>/task/<pid>/maps. Extending
is_proc_myself to cover these cases causes the maps to be rewritten
correctly.
These are useful in multithreaded programs to avoid freezing the
entire program to capture the maps for a single tid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1808565/+subscriptions
next reply other threads:[~2018-12-14 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:51 Alan Jones [this message]
2021-04-20 6:51 ` [Bug 1808565] Re: Reading /proc/self/task/<pid>/maps is not remapped to the target Thomas Huth
2021-04-20 9:22 ` Peter Maydell
2021-05-09 15:10 ` Thomas Huth
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=154480990326.22999.12064081216456974155.malonedeb@soybean.canonical.com \
--to=1808565@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).