From: Yao Qi <yao@codesourcery.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [MI][patch v2] -break-list to specify "thread-group"
Date: Sat, 22 Sep 2012 13:00:00 -0000 [thread overview]
Message-ID: <505DB611.70706@codesourcery.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5E11B177EA@EUSAACMS0703.eamcs.ericsson.se>
On 09/21/2012 10:46 PM, Marc Khouzam wrote:
> or (if the bp applies to multiple inferiors, which I didn't quite
> out how to officially trigger, so I hacked the code to make sure
> the output was done properly in that case):
>
I don't know ether. I can't think of a case that multiple inferiors
share a single pspace.
> Can this patch go in as is? Or can I get some guidance
> about how to handle this out-of-date MI output?
>
Maybe, we still need a test case for '-break-list' command here.
> #P src
> Index: gdb/breakpoint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/breakpoint.c,v
> retrieving revision 1.704
> diff -u -r1.704 breakpoint.c
> --- gdb/breakpoint.c 17 Sep 2012 07:03:14 -0000 1.704
> +++ gdb/breakpoint.c 21 Sep 2012 14:40:23 -0000
> @@ -69,6 +69,7 @@
> #include "gdb_regex.h"
> #include "ax-gdb.h"
> #include "dummy-frame.h"
> +#include "interps.h"
>
It is useless to include "interps.h" here.
> #include "format.h"
>
> @@ -5779,6 +5780,46 @@
> return bptypes[(int) type].description;
> }
>
> +/* Output a field named 'thread-group' with a list as the value. The
> + elements of the list are obtained by splitting 'groups' on
> + comma. */
> +
> +static void
> +output_thread_groups (struct ui_out *uiout, const char *field_name, const char *xgroups)
This line is too long.
The id of inferiors is passed in XGROUPS, why don't we pass an array of
integer? In this way, it is easier, IMO, and we don't have to parse string.
--
Yao
next prev parent reply other threads:[~2012-09-22 13:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 10:01 [MI][patch] " Marc Khouzam
2012-09-21 10:45 ` Marc Khouzam
2012-09-21 14:47 ` [MI][patch v2] " Marc Khouzam
2012-09-22 13:00 ` Yao Qi [this message]
2012-09-26 10:05 ` Marc Khouzam
2012-09-28 19:23 ` Tom Tromey
2012-10-01 16:10 ` Marc Khouzam
2012-10-01 16:17 ` Eli Zaretskii
2012-10-15 10:39 ` Marc Khouzam
2012-10-24 18:43 ` Marc Khouzam
2012-11-27 19:56 ` Marc Khouzam
2012-11-28 6:07 ` Abid, Hafiz
2012-11-30 18:35 ` Tom Tromey
2012-09-28 19:21 ` Tom Tromey
2012-12-07 15:37 ` Pedro Alves
2012-12-07 15:44 ` Pedro Alves
2013-01-16 16:58 ` Marc Khouzam
2013-01-21 18:54 ` Pedro Alves
2013-01-22 0:09 ` Marc Khouzam
2012-09-28 19:10 ` Tom Tromey
2012-09-28 19:18 ` Tom Tromey
2012-09-21 18:12 ` [MI][patch] " André Pönitz
2012-09-21 18:54 ` 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=505DB611.70706@codesourcery.com \
--to=yao@codesourcery.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