From: Guinevere Larsen <blarsen@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, btrace: fix error diagnostics
Date: Fri, 8 Mar 2024 10:07:41 +0100 [thread overview]
Message-ID: <a9bebb9d-c4b3-448b-9f08-bfb285dbd7a7@redhat.com> (raw)
In-Reply-To: <20240307150110.3348612-1-markus.t.metzger@intel.com>
On 07/03/2024 16:01, Markus Metzger wrote:
> When we improved error messages in
>
> cd393cec3ab gdb, btrace: improve error messages
>
> we cleared the original errno. When the error reason can not be explained
> in a more detailed error message, and we fall back to the default error
> message, it now gives Success as error.
>
> Restore the original errno to fix that.
Hi!
LGTM, Reviewed-By: Guinevere Larsen <blarsen@redhat.com>
--
Cheers,
Guinevere Larsen
She/Her/Hers
> ---
> gdb/nat/linux-btrace.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/nat/linux-btrace.c b/gdb/nat/linux-btrace.c
> index 50de2415589..f8352b62b8b 100644
> --- a/gdb/nat/linux-btrace.c
> +++ b/gdb/nat/linux-btrace.c
> @@ -422,7 +422,8 @@ cpu_supports_bts (void)
> static void
> diagnose_perf_event_open_fail ()
> {
> - switch (errno)
> + int orig_errno = errno;
> + switch (orig_errno)
> {
> case EPERM:
> case EACCES:
> @@ -443,7 +444,7 @@ diagnose_perf_event_open_fail ()
> break;
> }
>
> - error (_("Failed to start recording: %s"), safe_strerror (errno));
> + error (_("Failed to start recording: %s"), safe_strerror (orig_errno));
> }
>
> /* Get the linux version of a btrace_target_info. */
next prev parent reply other threads:[~2024-03-08 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 15:01 Markus Metzger
2024-03-08 9:07 ` Guinevere Larsen [this message]
2024-03-08 16:21 ` Tom Tromey
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=a9bebb9d-c4b3-448b-9f08-bfb285dbd7a7@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@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).