From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix gdb.ada/bp_c_mixed_case.exp (PR gdb/22670) (Re: [PATCH 3/3] Add new gdb.ada/bp_c_mixed_case testcase for PR gdb/22670)
Date: Tue, 09 Jan 2018 17:22:00 -0000 [thread overview]
Message-ID: <f5afb465-b1e8-ed43-fa83-5aa9e2f6656d@redhat.com> (raw)
In-Reply-To: <619dda09-5c48-447e-ead9-c9d6a5ac9743@redhat.com>
On 01/09/2018 04:45 PM, Pedro Alves wrote:
> On 01/09/2018 02:59 PM, Pedro Alves wrote:
>> On 01/09/2018 09:46 AM, Joel Brobecker wrote:
>
>>> What surprises me is that, before your patch, we were finding
>>> no symbol at all. So we were failing the lookup both with minimal
>>> symbols, and within the partial/full symtab.
>>
>> Indeed, good point. I don't know what I did not think of that.
>
> ...
>
>>> Does this make some kind of sense to you?
>>
>> Yes it does. I played with this a bit, and am testing a patch.
>> Stay tuned.
>
> How about this?
I pushed this to the users/palves/literal-matching branch too,
btw, for easier testing, along with a follow up patch to rename
language_get_symbol_name_matcher -> get_symbol_name_matcher,
since the function is no longer a straight "language method".
WDYT?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-01-09 17:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 8:36 FYI/pushed: Additional tests showing regression post C++ wild matching Joel Brobecker
2018-01-04 8:36 ` [PATCH 1/3] Add gdb.ada/info_addr_mixed_case new testcase Joel Brobecker
2018-01-04 13:25 ` Pedro Alves
2018-01-04 18:33 ` Pedro Alves
2018-01-05 3:22 ` Joel Brobecker
2018-01-05 16:06 ` Pedro Alves
2018-01-04 8:36 ` [PATCH 3/3] Add new gdb.ada/bp_c_mixed_case testcase for PR gdb/22670 Joel Brobecker
2018-01-05 16:34 ` Fix gdb.ada/bp_c_mixed_case.exp (PR gdb/22670) (Re: [PATCH 3/3] Add new gdb.ada/bp_c_mixed_case testcase for PR gdb/22670) Pedro Alves
2018-01-08 3:57 ` Joel Brobecker
2018-01-08 15:00 ` Pedro Alves
2018-01-09 9:46 ` Joel Brobecker
2018-01-09 14:59 ` Pedro Alves
2018-01-09 16:45 ` Pedro Alves
2018-01-09 17:22 ` Pedro Alves [this message]
2018-01-10 3:36 ` Joel Brobecker
2018-01-10 23:41 ` Pedro Alves
2018-01-11 4:00 ` Joel Brobecker
2018-01-04 8:36 ` [PATCH 2/3] Add "complete break ada" test to gdb.ada/complete.exp Joel Brobecker
2018-01-05 16:37 ` [PATCH] Fix gdb.ada/complete.exp's "complete break ada" test (PR, gdb/22670) (Re: [PATCH 2/3] Add "complete break ada" test to gdb.ada/complete.exp) Pedro Alves
2018-01-08 4:05 ` Joel Brobecker
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=f5afb465-b1e8-ed43-fa83-5aa9e2f6656d@redhat.com \
--to=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).