From: Pedro Alves <palves@redhat.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: Marcus Shawcroft <marcus.shawcroft@arm.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [native x86 GNU/Linux] Access debug register mirror from the corresponding inferior.
Date: Wed, 13 Feb 2013 15:14:00 -0000 [thread overview]
Message-ID: <511BADDB.3030703@redhat.com> (raw)
In-Reply-To: <511BA106.8030103@arm.com>
Aarch64 people,
I'll send you an aarch64 version of this patch, unless you've
already started porting the necessary bits over.
I think the only difference on AArch64 will be this comment:
/* Linux kernel before 2.6.33 commit
72f674d203cd230426437cdcf7dd6f681dad8b0d
will inherit hardware debug registers from parent
on fork/vfork/clone. Newer Linux kernels create such tasks with
zeroed debug registers.
GDB core assumes the child inherits the watchpoints/hw
breakpoints of the parent, and will remove them all from the
forked off process. Copy the debug registers mirrors into the
new process so that all breakpoints and watchpoints can be
removed together. The debug registers mirror will become zeroed
in the end before detaching the forked off process, thus making
this compatible with older Linux kernels too. */
Where I assume all AArch64 kernels zero the debug registers, so
that part of the comment gets dropped.
--
Pedro Alves
next prev parent reply other threads:[~2013-02-13 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:33 Pedro Alves
2013-02-07 16:59 ` Jan Kratochvil
2013-02-11 21:10 ` Pedro Alves
2013-02-12 12:36 ` Pedro Alves
2013-02-12 16:50 ` Jan Kratochvil
2013-02-13 15:04 ` Pedro Alves
2013-02-13 14:20 ` Yufeng Zhang
2013-02-13 14:51 ` Pedro Alves
2013-02-13 15:14 ` Pedro Alves [this message]
2013-02-13 15:21 ` Marcus Shawcroft
2013-02-13 16:02 ` [native AAarch64 GNU/Linux] Access debug register mirror from the corresponding process Pedro Alves
2013-02-13 18:57 ` Yufeng Zhang
2013-02-13 19:04 ` Pedro Alves
2013-02-14 10:13 ` Yufeng Zhang
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=511BADDB.3030703@redhat.com \
--to=palves@redhat.com \
--cc=Yufeng.Zhang@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@arm.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