public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	"Hannula, Ari" <ari.hannula@intel.com>
Cc: Tim Wiederhake <tim.wiederhake@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/5] [func_call] Add possible spelling of linker error message.
Date: Thu, 17 Mar 2022 11:45:46 -0700	[thread overview]
Message-ID: <1c8c2931-cb11-61dd-24d4-a30a1985e3ad@redhat.com> (raw)
In-Reply-To: <DM8PR11MB5749A6350E7B6F8964B8CC2DDE129@DM8PR11MB5749.namprd11.prod.outlook.com>

On 3/17/22 10:58, Metzger, Markus T wrote:
> Hello Ari,
> 
>> Seen with RHEL 7.5 and Fedora 26.
>>

Is there a little more that can be said? I gather this patch is
desired because the error message is simply different on some systems?

>> gdb/testsuite/ChangeLog:
>> 2019-02-18  Tim Wiederhake  <tim.wiederhake@intel.com>
>>
>> 	* lib/gdb.exp (gdb_compile_pthreads): Add new error regexp.
>>

As mentioned, you can drop these ChangeLog entries.

>> Signed-off-by: Tim Wiederhake <tim.wiederhake@intel.com>
>> Signed-off-by: Ari Hannula <ari.hannula@intel.com>
>> ---
>> gdb/testsuite/lib/gdb.exp | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
>> index a3717a4022..363289caa1 100644
>> --- a/gdb/testsuite/lib/gdb.exp
>> +++ b/gdb/testsuite/lib/gdb.exp
>> @@ -4618,6 +4618,9 @@ proc gdb_compile_pthreads {source dest type options}
>> {
>>                  set why_msg "missing threads include file"
>>                  break
>>              }
>> +            ".*cannot find -lpthread.*" {
>> +                set why_msg "missing runtime threads library"
>> +            }
>>              ".*cannot open -lpthread.*" {
>>                  set why_msg "missing runtime threads library"
>>              }

If these are truly the same error condition, then since this switch statement
uses regexp-matching, we should be able to merge the two "missing runtime
threads library" cases with "(find|open)".

If they are actually different errors, I'd like to see `why_msg' reflect the
distinction.

> LGTM but you need Keith or a global maintainer to approve this.

This otherwise looks okay to me, too, but I am unable to officially approve
patches.

Keith


  reply	other threads:[~2022-03-17 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 13:52 [PATCH 0/5] Functions call history patches Ari Hannula
2022-02-10 13:52 ` [PATCH 1/5] [func_call] Add possible spelling of linker error message Ari Hannula
2022-03-17 17:58   ` Metzger, Markus T
2022-03-17 18:45     ` Keith Seitz [this message]
2022-02-10 13:52 ` [PATCH 2/5] [func_call] New tests for a btrace crash Ari Hannula
2022-03-17 17:58   ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 3/5] [func_call] Fix MI output for function call history Ari Hannula
2022-03-17 17:58   ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 4/5] [func_call] Add function-call-history-length command to MI Ari Hannula
2022-03-17 17:59   ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 5/5] [func_call] Add function-call-history " Ari Hannula

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=1c8c2931-cb11-61dd-24d4-a30a1985e3ad@redhat.com \
    --to=keiths@redhat.com \
    --cc=ari.hannula@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=tim.wiederhake@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).