From: Yao Qi <yao@codesourcery.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Eli Zaretskii <eliz@gnu.org>, <tromey@redhat.com>,
<palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH v5][pushed] Exit code of exited inferiors in -list-thread-groups
Date: Mon, 13 Oct 2014 03:22:00 -0000 [thread overview]
Message-ID: <87mw90ody9.fsf@codesourcery.com> (raw)
In-Reply-To: <542C0F12.8090707@ericsson.com> (Simon Marchi's message of "Wed, 1 Oct 2014 10:26:26 -0400")
Simon Marchi <simon.marchi@ericsson.com> writes:
> diff --git a/gdb/testsuite/gdb.mi/mi-exit-code.c b/gdb/testsuite/gdb.mi/mi-exit-code.c
> new file mode 100644
> index 0000000..df711a6
> --- /dev/null
> +++ b/gdb/testsuite/gdb.mi/mi-exit-code.c
> @@ -0,0 +1,27 @@
> +/* Copyright 1999-2014 Free Software Foundation, Inc.
The copyright year should be 2013 - 2014, because mi-exit-code.c was
posted in 2013. This applies to mi-exit-code.exp too.
> +
> +int exit_code = 0;
> +
> +int
> +main (int argc, char **argv)
> +{
> + if (argc > 1)
> + exit_code = atoi (argv[1]);
I am looking at argv[] uses in gdb testsuite, and that is why I am
directed here. exit_code is set by gdb, so do we still need these two
lines above?
> +
> + return exit_code;
> +}
--
Yao (齐尧)
prev parent reply other threads:[~2014-10-13 3:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 21:56 [PATCH v5] " Simon Marchi
2014-05-14 2:51 ` Eli Zaretskii
2014-05-16 20:31 ` Tom Tromey
2014-05-21 17:34 ` Simon Marchi
2014-05-21 18:09 ` Pedro Alves
2014-05-23 18:57 ` Simon Marchi
2014-06-02 18:30 ` Simon Marchi
2014-06-02 18:37 ` Eli Zaretskii
2014-06-02 19:23 ` Pedro Alves
2014-06-02 20:20 ` Simon Marchi
2014-06-03 15:27 ` Pedro Alves
2014-06-04 18:09 ` Tom Tromey
2014-09-29 21:43 ` Simon Marchi
2014-09-29 21:45 ` Simon Marchi
2014-09-30 2:36 ` Eli Zaretskii
2014-10-01 14:26 ` [PATCH v5][pushed] " Simon Marchi
2014-10-13 3:22 ` Yao Qi [this message]
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=87mw90ody9.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
--cc=tromey@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