Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 	"Michael Snyder" <msnyder@vmware.com>,
	 	"Pedro Alves" <pedro@codesourcery.com>
Subject: [RFA] Displaced stepping just enable in non-stop mode
Date: Tue, 07 Oct 2008 06:27:00 -0000	[thread overview]
Message-ID: <daef60380810062326u442f166em1b1d2c1120a2c80b@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

Hi,

After communicated in http://sourceware.org/ml/gdb/2008-10/msg00019.html.
I make a patch make displaced stepping just enable in non-stop mode.

2008-10-07  Hui Zhu  <teawater@gmail.com>

	* infrun.c (use_displaced_stepping): Displaced stepping just
	enable in non-stop mode.

Thanks,
Hui

[-- Attachment #2: displaced_step_non_step.txt --]
[-- Type: text/plain, Size: 697 bytes --]

--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-10-07  Hui Zhu  <teawater@gmail.com>
+
+	* infrun.c (use_displaced_stepping): Displaced stepping just
+	enable in non-stop mode.
+
 2008-10-06  Doug Evans  <dje@google.com>
 
 	* dwarf2read.c (dwarf2_die_debug): New static global.
--- a/infrun.c
+++ b/infrun.c
@@ -568,11 +568,12 @@ Debugger's willingness to use displaced 
 }
 
 /* Return non-zero if displaced stepping is enabled, and can be used
-   with GDBARCH.  */
+   with GDBARCH, and in non-stop mode.  */
 static int
 use_displaced_stepping (struct gdbarch *gdbarch)
 {
   return (can_use_displaced_stepping
+	  && non_stop
 	  && gdbarch_displaced_step_copy_insn_p (gdbarch));
 }
 

             reply	other threads:[~2008-10-07  6:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07  6:27 teawater [this message]
2008-10-07 12:18 ` Joel Brobecker
2008-10-08  6:11   ` teawater
2008-10-09 14:50     ` Pedro Alves
2008-10-10  3:38       ` teawater
2008-10-14  7:36         ` teawater
2008-10-16  0:07           ` Pedro Alves
2008-10-16  2:29             ` teawater
2008-10-16  2:39             ` Daniel Jacobowitz
2008-10-16  2:59               ` Pedro Alves
2008-10-22  3:16                 ` teawater
2008-10-22 19:48                   ` Eli Zaretskii
2008-10-23  8:13                     ` teawater
2008-10-23 12:57                       ` Pedro Alves
2008-10-24  2:49                         ` teawater
2008-10-16  8:13             ` Eli Zaretskii
2008-10-16 12:35               ` Daniel Jacobowitz
2008-10-16 18:27                 ` Eli Zaretskii
2008-10-16 18:33                   ` Daniel Jacobowitz
2008-10-16 21:19                     ` Michael Snyder
2008-10-17  5:46                       ` teawater
2008-10-17 10:02                         ` Eli Zaretskii
2008-10-17 15:05                           ` Pedro Alves
2008-10-17 16:09                           ` teawater
2008-10-17 14:48                       ` Pedro Alves
2008-10-17 16:01                         ` teawater
2008-10-17 17:33                         ` Michael Snyder
2008-10-17 19:47                           ` Jakob Engblom
2008-10-17 19:49                             ` Michael Snyder
2008-10-17 14:51                   ` Pedro Alves
2008-10-17 15:53                     ` Eli Zaretskii

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=daef60380810062326u442f166em1b1d2c1120a2c80b@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@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