From: Pedro Alves <pedro@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org, drow@false.org, ross@tensilica.com
Subject: Re: RFC: Program Breakpoints
Date: Wed, 25 Mar 2009 13:17:00 -0000 [thread overview]
Message-ID: <200903251318.06153.pedro@codesourcery.com> (raw)
In-Reply-To: <200903250757.n2P7vQod004081@brahms.sibelius.xs4all.nl>
On Wednesday 25 March 2009 07:57:26, Mark Kettenis wrote:
> These statements are all rather i386-centric.
These were examples, not statements of all-truth. I mentioned
ppc-linux, and darwin; you meant hardware-single-stepping-centric.
> Especially on targets
> that emulate single-stepping it may be impossible to distinguish. GDB
> should not depend on the ability to do so.
If it's impossible to distinguish for some reason, then the target would
still report SIGTRAP-means-all, like today. When the distinction on the
debug api side is buggy and inconsistent, then GDB is better off
without it.
--
Pedro Alves
next prev parent reply other threads:[~2009-03-25 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 17:41 [RFC] stepping over permanent breakpoint Aleksandar Ristovski
2009-03-16 18:22 ` Pedro Alves
2009-03-16 18:55 ` Aleksandar Ristovski
2009-03-16 19:38 ` Pedro Alves
2009-03-16 20:37 ` Aleksandar Ristovski
2009-03-16 18:50 ` Mark Kettenis
2009-03-16 19:04 ` Aleksandar Ristovski
2009-03-23 16:50 ` RFC: Program Breakpoints (was: [RFC] stepping over permanent breakpoint) Ross Morley
2009-03-24 16:57 ` Daniel Jacobowitz
2009-03-24 20:33 ` RFC: Program Breakpoints Ross Morley
2009-03-24 20:40 ` Daniel Jacobowitz
2009-03-24 23:48 ` Pedro Alves
2009-03-25 7:58 ` Mark Kettenis
2009-03-25 13:17 ` Pedro Alves [this message]
2009-03-24 23:59 ` Ross Morley
2009-03-31 0:44 ` Ross Morley
2009-03-31 3:17 ` Daniel Jacobowitz
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=200903251318.06153.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=ross@tensilica.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