Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Amit Kale <amitkale@linsyssoft.com>
To: GDB patches <gdb-patches@sources.redhat.com>
Subject: [PATCH] preventing resuming of threads in gdbserver
Date: Tue, 10 Jan 2006 12:35:00 -0000	[thread overview]
Message-ID: <200601101805.31069.amitkale@linsyssoft.com> (raw)

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

Hi,

gdb lets other threads continue execution during single stepping when doing a 
single step in remote mode. This behavior causes thread switches during step 
or next commands. Native mode behavior is opposite of it. Attached patch 
changes it and makes it similar to native mode.

-Amit

[-- Attachment #2: gdb-noresumeallthreads.patch --]
[-- Type: text/x-diff, Size: 784 bytes --]

Index: gdb-cvs/gdb/remote.c
===================================================================
--- gdb-cvs.orig/gdb/remote.c	2006-01-03 11:24:35.000000000 +0530
+++ gdb-cvs/gdb/remote.c	2006-01-10 18:00:05.000000000 +0530
@@ -2519,10 +2519,10 @@
     {
       /* Resume all threads, with preference for INFERIOR_PTID.  */
       if (step && siggnal != TARGET_SIGNAL_0)
-	outbuf = xstrprintf ("vCont;S%02x:%x;c", siggnal,
+	outbuf = xstrprintf ("vCont;S%02x:%x", siggnal,
 			     PIDGET (inferior_ptid));
       else if (step)
-	outbuf = xstrprintf ("vCont;s:%x;c", PIDGET (inferior_ptid));
+	outbuf = xstrprintf ("vCont;s:%x", PIDGET (inferior_ptid));
       else if (siggnal != TARGET_SIGNAL_0)
 	outbuf = xstrprintf ("vCont;C%02x:%x;c", siggnal,
 			     PIDGET (inferior_ptid));

             reply	other threads:[~2006-01-10 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 12:35 Amit Kale [this message]
2006-01-10 21:20 ` Michael Snyder
2006-01-10 21:39   ` Daniel Jacobowitz
2006-01-11  7:35     ` Amit Kale
2006-01-11  7:17   ` Amit Kale

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=200601101805.31069.amitkale@linsyssoft.com \
    --to=amitkale@linsyssoft.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