public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: palves@redhat.com (Pedro Alves)
Cc: arnez@linux.vnet.ibm.com (Andreas Arnez), gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] S390: Watchpoint enhancements and hardware breakpoints
Date: Fri, 16 Sep 2016 12:43:00 -0000	[thread overview]
Message-ID: <20160916124323.AE052FE999@oc8523832656.ibm.com> (raw)
In-Reply-To: <8b5f2062-d755-672d-a899-781f77baa921@redhat.com> from "Pedro Alves" at Sep 15, 2016 03:11:02 PM

Pedro Alves wrote:
> On 09/15/2016 12:52 PM, Andreas Arnez wrote:
> > This series adds some enhancements to the current s390-linux native
> > support for watchpoints.  It also adds hardware breakpoint support.
> > 
> > While this is mostly an s390-specific series, it includes one
> > common-code patch: patch #5, "linux-nat: Add function lwp_is_stepping".
> > I'm looking for feedback on that.  Comments to the s390-specific patches
> > are certainly welcome as well.
> 
> I'm curious on the need to disable hw breakpoints when single-stepping.

This is more of a hardware restriction than a GDB issue.  The problem is
that s390 hardware doesn't really have a separate hardware single-step
feature; to implement ptrace single-stepping, the kernel uses the s390
hardware breakpoint feature (in effect, enabling hardware breakpoints
on the full address space, which will hit on the next instruction that
is executed).

This use of the feature by kernel single-stepping can conflict with
explicit use of the same feature by GDB; that's why it is better to
not attempt such explicit use while at the same time also requesting
kernel single-stepping.

Bye,
Ulrich

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

  reply	other threads:[~2016-09-16 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 11:53 Andreas Arnez
2016-09-15 11:54 ` [PATCH] Fix order of inferiors in "thread apply all" Andreas Arnez
2016-09-15 12:03   ` Andreas Arnez
2016-09-15 11:59 ` [PATCH 1/6] S390: Avoid direct access to lwp_info structure Andreas Arnez
2016-09-15 12:01 ` [PATCH 3/6] S390: Multi-inferior watchpoint support Andreas Arnez
2016-09-15 12:02 ` [PATCH 5/6] linux-nat: Add function lwp_is_stepping Andreas Arnez
2016-09-15 15:08   ` Yao Qi
2016-09-15 12:02 ` [PATCH 6/6] S390: Hardware breakpoint support Andreas Arnez
2016-09-15 12:02 ` [PATCH 2/6] S390: Migrate watch areas from list to VEC type Andreas Arnez
2016-09-15 12:02 ` [PATCH 4/6] S390: Enable "maint set show-debug-regs" Andreas Arnez
2016-09-15 14:11 ` [PATCH 0/6] S390: Watchpoint enhancements and hardware breakpoints Pedro Alves
2016-09-16 12:43   ` Ulrich Weigand [this message]
2016-09-16 15:43     ` Pedro Alves
2016-09-16 17:30       ` Andreas Arnez
2016-09-15 14:58 ` Yao Qi
2016-09-15 17:14   ` Andreas Arnez

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=20160916124323.AE052FE999@oc8523832656.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).