From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Always use at least schedlock_step for software single step targets
Date: Fri, 06 Jun 2003 21:36:00 -0000 [thread overview]
Message-ID: <3EE1096D.8030801@redhat.com> (raw)
In-Reply-To: <20030605143728.GA31355@nevyn.them.org>
> It effectively forces schedlock_step for SSS targets
> (but I guess you knew that). People appear to be very
> diverse in their opinion about whether schedlock is the
> "right" behavior or the "wrong" one. You might not see
> the behavior that you're trying to debug, if you're only
> stepping one thread.
There are targets for which sched lock almost meaningless, but then,
hopefully those targets also support hardware single step.
The change looks to be the best option.
Andrew
next prev parent reply other threads:[~2003-06-06 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 14:37 Daniel Jacobowitz
2003-06-05 18:44 ` Michael Snyder
2003-06-05 18:47 ` Daniel Jacobowitz
2003-06-05 19:04 ` Michael Snyder
2003-06-06 21:36 ` Andrew Cagney [this message]
2003-06-06 23:58 ` 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=3EE1096D.8030801@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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