Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb-patches\@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [MI][patch] broken -target-detach
Date: Tue, 12 Oct 2010 22:51:00 -0000	[thread overview]
Message-ID: <m3tykrf2j4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC571AB036DD@EUSAACMS0703.eamcs.ericsson.se>	(Marc Khouzam's message of "Wed, 29 Sep 2010 21:35:29 -0400")

>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:

I'm sorry about the delay.

I recommend pinging your patches weekly.

Marc> Using the --thread-group flag (alike -thread and --frame) tells the MI
Marc> command to focus on the thread-group specified and then execute the
Marc> command.  

It seems reasonable to me.

Marc> +         /* We are not dealing with a pid.  Check for group id */
Marc> +         if (*(argv[0]) != 'i')
Marc> +           error (_("Invalid pid or thread-group id '%s'"), argv[0]);
Marc> +
Marc> +         id = strtoul (argv[0] + 1, &end, 0);
Marc> +         if (*end != '\0')
Marc> +           error (_("Invalid syntax of group id '%s'"), argv[0]);

This code is duplicated in various spots in MI.  Seems ugly -- but not
your problem.


I think this patch looks good.  It needs a ChangeLog entry.  A test case
would be nice to have.

I think it would be better for Volodya to review it, since he is the MI
maintainer.  If he doesn't review it within a week or so, please ping it
and I will approve it.

thanks,
Tom


  reply	other threads:[~2010-10-12 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28  9:21 Marc Khouzam
2010-09-30 10:25 ` Marc Khouzam
2010-10-12 22:51   ` Tom Tromey [this message]
2010-10-15 23:47 ` Pedro Alves
2010-11-12 16:02   ` Marc Khouzam
2010-11-12 16:43     ` Pedro Alves
2010-11-12 19:07       ` 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=m3tykrf2j4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.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