From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [MI][Patch] -exec-continue/interrupt --thread-group expects wrong id
Date: Fri, 05 Jun 2009 18:36:00 -0000 [thread overview]
Message-ID: <h0boho$kq9$1@ger.gmane.org> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA0789E1B2@ecamlmw720.eamcs.ericsson.se>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Marc Khouzam wrote:
> Hi,
>
> After Pedro kindly pointed out that there is a
> --thread-group parameter to -exec-continue and -exec-interrupt
> (how did I miss that?) I tried them out.
> I found that they still expect the old form of the
> threadGroupId (starting with a 'p').
>
> The patch below fixes both methods.
>
> This is hard to test since HEAD does not have a fully functional
> multi-process, but I was able to confirm that the threadGroupId
> gets properly accepted with my patch.
Thanks, I have applied this patch as attached. Please include changelog
entry for future patch submissions though -- somebody still has to write
them before "cvs commit" :-)
- Volodya
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: final.diff --]
[-- Type: text/x-diff; name="final.diff", Size: 1545 bytes --]
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.10553
diff -u -p -r1.10553 ChangeLog
--- ChangeLog 5 Jun 2009 18:08:52 -0000 1.10553
+++ ChangeLog 5 Jun 2009 18:33:36 -0000
@@ -1,3 +1,9 @@
+2009-06-05 Marc Khouzam <marc.khouzam@ericsson.com>
+
+ * mi/mi-main.c (mi_cmd_exec_continue)
+ (mi_cmd_exec_interrupt): Adjust parsing of thread group
+ ids to current reality, where they don't have any 'p' prefix.
+
2009-06-05 Aleksandar Ristovski <aristovski@qnx.com>
* corelow.c (core_open): Check for core_gdbarch before calling
Index: mi/mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.149
diff -u -p -r1.149 mi-main.c
--- mi/mi-main.c 28 May 2009 01:09:20 -0000 1.149
+++ mi/mi-main.c 5 Jun 2009 18:33:37 -0000
@@ -205,7 +205,7 @@ mi_cmd_exec_continue (char *command, cha
int pid;
if (argv[1] == NULL || argv[1] == '\0')
error ("Thread group id not specified");
- pid = atoi (argv[1] + 1);
+ pid = atoi (argv[1]);
if (!in_inferior_list (pid))
error ("Invalid thread group id '%s'", argv[1]);
@@ -260,7 +260,7 @@ mi_cmd_exec_interrupt (char *command, ch
int pid;
if (argv[1] == NULL || argv[1] == '\0')
error ("Thread group id not specified");
- pid = atoi (argv[1] + 1);
+ pid = atoi (argv[1]);
if (!in_inferior_list (pid))
error ("Invalid thread group id '%s'", argv[1]);
next prev parent reply other threads:[~2009-06-05 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 17:34 Marc Khouzam
2009-06-05 18:36 ` Vladimir Prus [this message]
2009-06-05 18:42 ` Marc Khouzam
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='h0boho$kq9$1@ger.gmane.org' \
--to=vladimir@codesourcery.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