From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][TEST-CASE][DOC] Implementation of pipe to pass GDB's command output to a shell command.
Date: Fri, 02 Sep 2011 21:04:00 -0000 [thread overview]
Message-ID: <20110902204454.GA23897@host1.jankratochvil.net> (raw)
In-Reply-To: <CAOhZP9wR64nEfvJgtv=1Nby+7mpCavrxsXfUWG+SaeJMO2ynJA@mail.gmail.com>
On Wed, 31 Aug 2011 17:09:30 +0200, Abhijit Halder wrote:
> --- src/gdb/pipe.c 2011-07-29 15:15:26.078048517 +0530
> +++ dst/gdb/pipe.c 2011-08-29 18:50:14.000000000 +0530
[...]
> +#if defined(__MINGW32__)
->
+#if defined (__MINGW32__)
Not GNU Coding Style compliant although it is so common in GDB I do not mind
(already commented before).
> +# define SHELL "cmd.exe"
> +# define OPTION_TO_SHELL "/c"
> +#else
> +# define SHELL "/bin/sh"
> +# define OPTION_TO_SHELL "-c"
> +#endif
[...]
> --- src/gdb/testsuite/gdb.base/pipe.exp 2011-08-16 22:37:45.969351119 +0530
> +++ dst/gdb/testsuite/gdb.base/pipe.exp 2011-08-25 03:10:05.000000000 +0530
> @@ -0,0 +1,52 @@
[...]
> + regsub -all {\$[0-9]+} $fdata {} pattern
> + if ![string match $pattern " = 120 'x'\n"] then {
Instead of regsub + string match just:
if ![string match "* = 120 'x'\n" $fdata] then {
You have opposite order of the pattern vs. string in the `string match'
otherwise.
> + fail $test
> + } else {
> + pass $test
> + }
> +}
next prev parent reply other threads:[~2011-09-02 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 15:09 Abhijit Halder
2011-09-02 21:04 ` Jan Kratochvil [this message]
2011-09-03 9:32 ` Abhijit Halder
2011-09-04 15:05 ` Jan Kratochvil
2011-09-04 17:05 ` Abhijit Halder
2011-09-05 11:56 ` Abhijit Halder
2011-09-05 15:57 ` Abhijit Halder
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=20110902204454.GA23897@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=abhijit.k.halder@gmail.com \
--cc=gdb-patches@sourceware.org \
/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