From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "Hannula, Ari" <ari.hannula@intel.com>
Cc: Tim Wiederhake <tim.wiederhake@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"keiths@redhat.com" <keiths@redhat.com>
Subject: RE: [PATCH 1/5] [func_call] Add possible spelling of linker error message.
Date: Thu, 17 Mar 2022 17:58:36 +0000 [thread overview]
Message-ID: <DM8PR11MB5749A6350E7B6F8964B8CC2DDE129@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220210135243.3127629-2-ari.hannula@intel.com>
Hello Ari,
>Seen with RHEL 7.5 and Fedora 26.
>
>gdb/testsuite/ChangeLog:
>2019-02-18 Tim Wiederhake <tim.wiederhake@intel.com>
>
> * lib/gdb.exp (gdb_compile_pthreads): Add new error regexp.
>
>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"
> }
>--
>2.25.1
LGTM but you need Keith or a global maintainer to approve this.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-03-17 17:59 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 [this message]
2022-03-17 18:45 ` Keith Seitz
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=DM8PR11MB5749A6350E7B6F8964B8CC2DDE129@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=ari.hannula@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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).