Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 21 Aug 2019 17:45:00 -0000	[thread overview]
Message-ID: <871rxefm5m.fsf@linux.ibm.com> (raw)
In-Reply-To: <20190821153133.B457CD802EF@oc3748833570.ibm.com>

"Ulrich Weigand" <uweigand@de.ibm.com> writes:

> 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.

I think it's easier to do it in prepare_to_resume, since we have to do
it there anyway to handle hardware breakpoints that were removed by the
user.  I'm also not sure that linux-nat is prepared to take exceptions
from these callbacks, in case a ptrace call there fails.

> 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.

Ok.  Is it acceptable if linux-low in gdbserver doesn't have the
equivalent hook?  Adding one there would require changing struct
linux_target_ops and every arch that uses it.  This will become
necessary in the future to enable hardware breakpoints in the ppc server
stub.

Thanks!

--
Pedro Franco de Carvalho

>
> Thanks,
> Ulrich
>
> -- 
>   Dr. Ulrich Weigand
>   GNU/Linux compilers and toolchain
>   Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2019-08-21 17:45 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
2019-08-21 17:45   ` Pedro Franco de Carvalho [this message]
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=871rxefm5m.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