From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat
Date: Fri, 09 Aug 2019 15:53:00 -0000 [thread overview]
Message-ID: <87tvaq72u8.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190809152845.C680AD802D2@oc3748833570.ibm.com>
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
> But it seems what would work reliably is to delete slots from 1 to max,
> while ignoring ENOENT, right? In fact, you don't even need to know the
> max slot number, because you'll get EINVAL if and only if you're attempting
> to delete the first slot after max (assuming you do it in sequence).
Yes, this should work and should make the next version simpler. I'll
make a new version of the patch.
Thanks!
--
Pedro Franco de Carvalho
next prev parent reply other threads:[~2019-08-09 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 2/3] [PowerPC] Move up some register access routines Pedro Franco de Carvalho
2019-08-08 16:25 ` Ulrich Weigand
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 [this message]
2019-07-26 12:50 ` [PATCH 1/3] Add low_new_clone method to linux_nat_target Pedro Franco de Carvalho
2019-08-08 14:05 ` Ulrich Weigand
[not found] <87ftm56uqg.fsf@linux.ibm.com>
2019-08-21 15:31 ` [PATCH 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Ulrich Weigand
2019-08-21 17:45 ` Pedro Franco de Carvalho
2019-08-22 10:27 ` Ulrich Weigand
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=87tvaq72u8.fsf@linux.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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