Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pedro@codesourcery.com
Cc: gdb-patches@sourceware.org, yao@codesourcery.com
Subject: Re: [patch] Skip kill-after-signal.exp if hw single-step is not supported
Date: Sun, 24 Jul 2011 11:40:00 -0000	[thread overview]
Message-ID: <201107232247.p6NMlwVx029216@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <201107201605.43767.pedro@codesourcery.com> (message from Pedro	Alves on Wed, 20 Jul 2011 16:05:43 +0100)

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 20 Jul 2011 16:05:43 +0100
> 
> Other archs !x86, and other kernels/stubs/servers !Linux that
> can do hardware stepping.  If we're going to have a list, invert
> the logic of the check, defaulting to running the test, and leaving
> out archs were we know software stepping is used.  Some targets,
> like x86/OpenBSD and MacOS, although can hardware step, can't step
> into a handler.

Just FYI, it's putting breakpoints into the signal trampoline that is
the issue, at least on OpenBSD.  Single-stepping should work fine on
OpenBSD/i386 and OpenBSD/amd64 and all other architectures where it's
done in hardware.


  reply	other threads:[~2011-07-23 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 14:52 Yao Qi
2011-07-20 15:06 ` Jan Kratochvil
2011-07-20 15:12 ` Pedro Alves
2011-07-24 11:40   ` Mark Kettenis [this message]
2011-08-09 14:32     ` Yao Qi
2011-08-09 15:24       ` Matthew Gretton-Dann
2011-08-09 15:50         ` Yao Qi
2011-08-18  4:53       ` ping : " Yao Qi
2011-08-28 14:44         ` Yao Qi
2011-09-14  7:18       ` ping 3: " Yao Qi
2011-09-18  2:42       ` Joel Brobecker
2011-09-18 10:22         ` [committed]: " Yao Qi
2011-07-23 23:28 ` Mark Kettenis

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=201107232247.p6NMlwVx029216@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=yao@codesourcery.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