public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] regresssion(internal-error) printing subprogram argument
Date: Thu, 04 Jan 2018 12:39:00 -0000	[thread overview]
Message-ID: <851cef1b-0ba8-6c19-1296-d455b21207e5@redhat.com> (raw)
In-Reply-To: <20180104094839.ptve3hy4fndifr27@adacore.com>

Hi Joel,
On 01/04/2018 09:48 AM, Joel Brobecker wrote:
> Hi Pedro,
> 
> FYI, I just pushed 3 commits that add more testing in gdb.ada
> demonstrating issues introduced by the wild-matching patch series
> I hadn't noticed before. See:
> 
> https://www.sourceware.org/ml/gdb-patches/2018-01/msg00052.html
> 
> As hinted by the ChangeLog entries, I have also created PR gdb/22670
> so as to be able to KFAIL the expected failures. And now that we have
> this PR, we can use it to track the fixes as well ;-).
> 
> I also pushed the patch which adds "maint check psymtabs" testing;
> also with a setup_kfail.
> 
> Here is my plan: I will continue going through the results I get
> when running AdaCore's GDB testsuite (almost there). If there are
> other tests related to this patch series, I will try to contribute
> those as well. Once I'm doing analyzing the current results, I will
> start investigating those failures one by one, and let you know
> what I find. For now, all I know is that litteral matching is not
> enough to fix those, so I am not sure what is happening just yet.
> I will let you know!

Thanks!  I'm catching up to this and will take a look at the
new tests.

Pedro Alves

  reply	other threads:[~2018-01-04 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 10:37 Joel Brobecker
2017-12-14 19:02 ` Pedro Alves
2017-12-14 19:41   ` Pedro Alves
2017-12-15  9:48     ` Joel Brobecker
2017-12-15 11:02       ` Pedro Alves
2017-12-15 18:57         ` Pedro Alves
2018-01-03  4:33           ` Joel Brobecker
2018-01-04  9:48             ` Joel Brobecker
2018-01-04 12:39               ` Pedro Alves [this message]
2018-01-05 16:28             ` Pedro Alves
2018-01-16 11:54               ` Pedro Alves
2018-01-17  9:13                 ` Joel Brobecker
2018-01-26  3:51                   ` Joel Brobecker
2018-01-26 11:28                     ` Pedro Alves
2018-01-29 10:38                       ` Joel Brobecker
2018-01-29 15:33                         ` Pedro Alves
2018-01-29 15:52                           ` Joel Brobecker
2018-01-30  3:56                           ` Joel Brobecker
2018-02-05  9:57                             ` Joel Brobecker
2018-02-09  9:09                               ` [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name) (was: "Re: [RFC] regresssion(internal-error) printing subprogram argument") Joel Brobecker
2018-02-21  3:02                                 ` PING: " Joel Brobecker
2018-03-19 21:22                                   ` PING^2: " Joel Brobecker
2018-03-26 14:26                                     ` PING^2: [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name) Pedro Alves
2018-03-27 14:02                                       ` Joel Brobecker
2018-01-26  4:50                   ` [RFC] regresssion(internal-error) printing subprogram argument Joel Brobecker
2017-12-15 18:31       ` Pedro Alves
2017-12-15  7:54   ` 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=851cef1b-0ba8-6c19-1296-d455b21207e5@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).