From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedromfc@linux.ibm.com (Pedro Franco de Carvalho)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat
Date: Wed, 21 Aug 2019 15:31:00 -0000 [thread overview]
Message-ID: <20190821153133.B457CD802EF@oc3748833570.ibm.com> (raw)
In-Reply-To: <87ftm56uqg.fsf@linux.ibm.com> from "Pedro Franco de Carvalho" at Aug 13, 2019 10:49:27 AM
Pedro Franco de Carvalho wrote:
> I don't think this is the way the interface was intended to be used (see
> linux/Documentation/powerpc/ptrace.txt),
You're right. Any attempt to be "clever" like this must necessarily
make assumptions that go beyond treating the return value of
PTRACE_SETHWDEBUG as opaque handle. I didn't realize this ...
> Is this an acceptable solution, or should we keep track of installed
> slots across clones and forks?
Given the above, I guess I now agree with your originally proposed
solution to keep track of installed slots across clones and forks.
The one question I still have is, given that we'll be deleting the
installed breakpoints after a clone/fork anyway, wouldn't it be
easier to just *delete* all breakpoints directly at the clone/fork
callback and start out the GDB "installed" structures as empty?
But that's just a minor detail ... whatever is easier to implement
is fine with me.
Since this really seems to be required on PowerPC due to the peculiar
ptrace interface, I'm fine with adding the common code clone hook.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next parent reply other threads:[~2019-08-21 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ftm56uqg.fsf@linux.ibm.com>
2019-08-21 15:31 ` Ulrich Weigand [this message]
2019-08-21 17:45 ` Pedro Franco de Carvalho
2019-08-22 10:27 ` Ulrich Weigand
2019-07-26 12:50 [PATCH 0/3] low_new_clone in linux-nat.c and powerpc watchpoint fixes Pedro Franco de Carvalho
2019-07-26 12:50 ` [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Pedro Franco de Carvalho
2019-08-08 16:24 ` Ulrich Weigand
2019-08-08 20:27 ` Pedro Franco de Carvalho
2019-08-09 11:04 ` Ulrich Weigand
2019-08-09 15:04 ` Pedro Franco de Carvalho
2019-08-09 15:28 ` Ulrich Weigand
2019-08-09 15:53 ` Pedro Franco de Carvalho
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=20190821153133.B457CD802EF@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedromfc@linux.ibm.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