public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: [PATCH] gdb_disassemble_driver: "thread" not "threads"
Date: Tue, 28 Aug 2001 15:22:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0108281519030.2633-100000@makita.cygnus.com> (raw)

Hi,

This patch changes one of the criteria for debugging a child process from
looking for "threads" in the target's shortname to "thread" in the name.

This should fix disassembly problems on multi-threaded linux applications.

Keith

ChangeLog
2001-08-28  Keith Seitz  <keiths@redhat.com>

	* generic/gdbtk-cmds.c (gdb_disassemble_driver): We should be
	looking for "thread", not "threads" to determine if we have
	a multi-threaded child process.

Patch
Index: generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.38
diff -u -p -r1.38 gdbtk-cmds.c
--- gdbtk-cmds.c	2001/08/20 17:55:31	1.38
+++ gdbtk-cmds.c	2001/08/28 22:21:40
@@ -2130,7 +2130,7 @@ gdb_disassemble_driver (low, high, mixed
       if (strcmp (target_shortname, "child") == 0
           || strcmp (target_shortname, "procfs") == 0
           || strcmp (target_shortname, "vxprocess") == 0
-	  || strstr (target_shortname, "threads") != NULL)
+	  || strstr (target_shortname, "thread") != NULL)
 	/* It's a child process, read inferior mem */
         disassemble_from_exec = 0;
       else

                 reply	other threads:[~2001-08-28 15:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.GSO.4.33.0108281519030.2633-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).