From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Expect for "@" when doing "complete break ada" on gdb.ada/complete.exp
Date: Tue, 18 Sep 2018 17:51:00 -0000 [thread overview]
Message-ID: <875zz2zobn.fsf@redhat.com> (raw)
In-Reply-To: <20180918150327.GK19172@adacore.com> (Joel Brobecker's message of "Tue, 18 Sep 2018 08:03:27 -0700")
On Tuesday, September 18 2018, Joel Brobecker wrote:
> Hi Sergio,
Hey Joel,
> Thanks for the patch!
My pleasure :-).
>> Currently, gdb.ada/complete.exp's "complete break ada" test fails
>> because the regexp used to match the command's output doesn't expect
>> "@", but we have an output like:
>>
>> ...
>> complete break ada
>> break ada.assertions.assert
>> break ada.calendar.arithmetic.difference
>> break ada.calendar.arithmetic_operations.add
>> break ada.calendar.arithmetic_operations.add.cold
>> break ada.calendar.arithmetic_operations.add@plt
>> break ada.calendar.arithmetic_operations.difference
>> break ada.calendar.arithmetic_operations.difference@plt
>> ...
>>
>> This patch adds "@" to the regexp, unbreaking the test.
>>
>> OK?
>>
>> gdb/testsuite/ChangeLog:
>> 2018-09-17 Sergio Durigan Junior <sergiodj@redhat.com>
>>
>> * gdb.ada/complete.exp: Expect for "@" when doing "complete
>> break ada".
>
> I can see this behavior, but only when I link with the shared
> version of libgnat. For us at least, on x86_64-linux, this is not
> the default. That's probably why I wasn't seeing this.
Ah, I see. TBH, I haven't investigate this further. I'm glad you can
reproduce it there.
> This is OK.
Thanks, pushed.
7a6d2b458f95030f433a0dcdabd5cda7ee695a9b
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-09-18 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 21:33 Sergio Durigan Junior
2018-09-18 15:03 ` Joel Brobecker
2018-09-18 17:51 ` Sergio Durigan Junior [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=875zz2zobn.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.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