From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pierre-Marie de Rodat <derodat@adacore.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Pedro Alves <palves@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Share the "multi_line" helper among all Ada testcases
Date: Mon, 20 Jul 2015 15:35:00 -0000 [thread overview]
Message-ID: <87r3o2rgeh.fsf@redhat.com> (raw)
In-Reply-To: <55AD0A6E.6060604@adacore.com> (Pierre-Marie de Rodat's message of "Mon, 20 Jul 2015 16:49:18 +0200")
Hey Pierre,
On Monday, July 20 2015, Pierre-Marie de Rodat wrote:
> On 07/18/2015 02:35 AM, Sergio Durigan Junior wrote:
>> Hmm, I am seeing a regression on gdb.ada/info_exc.exp because of this
>> patch. Because of the way multi_line was rewritten it is not possibe
>> anymore to mean "anything" again; it will always be at least a newline
>> (\r\n).
>>
>> I've rewritten the test to expect the exact output from "info
>> exceptions" (i.e., removing the ".*" parts), but I am not sure this is
>> the right thing to do. Joel/Pierre?
>
> Thank you for the heads-up! I did not notice this when submitting the
> patch... Anyway, I had a look at what commit introduced the ".*"
> parts:
>
> commit 391d3400084c6a2d805cd0efd925f29347fa7a18
> Author: Joel Brobecker <brobecker@adacore.com>
> Date: Fri Nov 15 20:34:09 2013 +0400
>
> gdb.ada/info_exc.exp,mi_exc_info.exp: handle runtimes with full
> debug info.
>
> If the runtime has full debug info, then the non-standard exceptions
> declared in the GNAT runtime will appear in the list of exceptions
> printed by GDB ("info exceptions" or "-info-ada-exceptions").
> This is valid output, so this patch allows for it.
>
> So it looks like they are needed for some configuration. Then, what
> about this:
Hm, right, thanks for checking this. I suspected that the ".*" had a
reason to exist...
> diff --git a/gdb/testsuite/gdb.ada/info_exc.exp
> b/gdb/testsuite/gdb.ada/info_exc.exp
> index add83c5..448882b 100644
> --- a/gdb/testsuite/gdb.ada/info_exc.exp
> +++ b/gdb/testsuite/gdb.ada/info_exc.exp
> @@ -34,9 +34,7 @@ gdb_test "info exceptions" \
> "program_error: $hex" \
> "storage_error: $hex" \
> "tasking_error: $hex" \
> - ".*" \
> - "const.aint_global_gdb_e: $hex" \
> - ".*"]
> + "\(.*\r\n\)*const.aint_global_gdb_e: $hex\(.*\r\n\)*"]
>
> gdb_test "info exceptions task" \
> [multi_line "All Ada exceptions matching regular expression
> \"task\":" \
The patch looks good to me and works fine here (though I haven't tested
the case when the output contains more lines than expected). I'm not a
maintainer of this area, so I cannot really approve this.
Thanks!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-07-20 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:55 Pierre-Marie de Rodat
2015-03-17 20:08 ` Joel Brobecker
2015-03-18 9:45 ` Pedro Alves
2015-03-18 14:12 ` Joel Brobecker
2015-03-20 12:18 ` Pierre-Marie de Rodat
2015-03-20 18:00 ` Pedro Alves
2015-04-01 8:50 ` Pierre-Marie de Rodat
2015-04-01 10:26 ` Pedro Alves
2015-04-01 13:08 ` Pierre-Marie de Rodat
2015-07-18 0:35 ` Sergio Durigan Junior
2015-07-20 14:49 ` Pierre-Marie de Rodat
2015-07-20 15:35 ` Sergio Durigan Junior [this message]
2015-07-20 22:23 ` Joel Brobecker
2015-07-20 22:42 ` Sergio Durigan Junior
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=87r3o2rgeh.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=derodat@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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