From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat
Date: Mon, 30 Mar 2020 12:13:57 -0300 [thread overview]
Message-ID: <874ku5q3ii.fsf@linux.ibm.com> (raw)
In-Reply-To: <20200330130331.C3502D803A1@oc3748833570.ibm.com>
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
Hello,
> Sorry for the late reply to the previous mail. I agree that this
> approach is probably the best for now. The ESRCH issue is a pre-
> existing problem; if we want to address it in the future, this can
> still be done as a follow-on.
Ok! Strictly speaking only the HWDEBUG interface would be unavailable
for the duration of the GDB session in the previous version of the code,
the DEBUGREG one would still be tried the next time. The current one
would have neither. But I do think worth sacrificing this improbable
case for more clarity in the interface detection code.
I've checked the patches in. Thanks a lot for the reviews!!
--
Pedro Franco de Carvalho
next prev parent reply other threads:[~2020-03-30 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 20:55 [PATCH v2 0/3] low_new_clone in linux-nat.c and powerpc watchpoint fixes Pedro Franco de Carvalho
2020-02-14 20:55 ` [PATCH v2 2/3] [PowerPC] Move up some register access routines Pedro Franco de Carvalho
2020-02-17 17:48 ` Ulrich Weigand
2020-02-14 20:55 ` [PATCH v2 3/3] [PowerPC] Fix debug register issues in ppc-linux-nat Pedro Franco de Carvalho
2020-02-17 17:47 ` Ulrich Weigand
2020-02-18 20:31 ` Pedro Franco de Carvalho
2020-02-19 13:46 ` Ulrich Weigand
2020-03-13 20:19 ` Pedro Franco de Carvalho
2020-03-27 18:50 ` Pedro Franco de Carvalho
2020-03-27 18:54 ` [PATCH] " Pedro Franco de Carvalho
2020-03-30 13:04 ` Ulrich Weigand
2020-03-30 13:03 ` [PATCH v2 3/3] " Ulrich Weigand
2020-03-30 15:13 ` Pedro Franco de Carvalho [this message]
2020-02-14 20:55 ` [PATCH v2 1/3] Add low_new_clone method to linux_nat_target Pedro Franco de Carvalho
2020-02-17 17:49 ` 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=874ku5q3ii.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