public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
	 Yao Qi <qiyaoltc@gmail.com>,  <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdbserver] Disable conditional breakpoints on no-hardware-single-step targets
Date: Fri, 08 May 2015 13:14:00 -0000	[thread overview]
Message-ID: <86lhgztdoq.fsf@gmail.com> (raw)
In-Reply-To: <554CA972.8050700@codesourcery.com> (Luis Machado's message of	"Fri, 8 May 2015 09:17:54 -0300")

Luis Machado <lgustavo@codesourcery.com> writes:

> I like the idea of having gdbserver learn how to properly
> software-single-step, allowing us to share the knowledge GDB already
> has.

Yes, I like this idea too, but I am still unsure how complicated
execution control in GDBserver will be after software-single-step is
added in GDBserver.

>
> Disabling a feature, on the other hand, sound like a backward movement.
>

I disable this feature on non-hardware-single-step targets, because
these targets don't know how to do precise software single step.  I
don't know when GDBserver can do software single step, IMO, it's better
to disable this feature.

> People with knowledge on each architecture can probably help fine tune
> those to their needs.

Yes, we can do improvements in this way, however, in this case, the
feature is somewhat broken on some targets, we either fix it or disable it.

-- 
Yao (齐尧)

  reply	other threads:[~2015-05-08 13:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1430411029-12097-1-git-send-email-qiyaoltc@gmail.com>
     [not found] ` <55426205.3070901@ericsson.com>
2015-05-01 14:18   ` Yao Qi
2015-05-08 12:18   ` Luis Machado
2015-05-08 13:14     ` Yao Qi [this message]
2015-05-06 15:43 ` Pedro Alves
2015-05-07 10:48   ` Yao Qi
2015-05-07 11:45     ` Antoine Tremblay
2015-05-08 11:50       ` Pedro Alves
2015-05-08 12:12         ` Antoine Tremblay
2015-05-08 12:29           ` Pedro Alves
2015-05-08 12:35             ` Antoine Tremblay
2015-05-08 11:02     ` Pedro Alves
2015-05-10  1:04   ` Maciej W. Rozycki
2015-05-11 11:31     ` Pedro Alves
2015-05-11 12:38       ` Maciej W. Rozycki
2015-05-11 14:08         ` Pedro Alves
2015-05-11 17:40           ` Maciej W. Rozycki

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=86lhgztdoq.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=antoine.tremblay@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).