public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29999] Bogus error message printed when debuginfod doesn't find source file
Date: Sat, 11 Feb 2023 02:12:01 +0000	[thread overview]
Message-ID: <bug-29999-4717-gRVJtqcwXX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29999-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29999

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aaron Merey <amerey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8cc96ee4169f631917d048cbaeec14ddf8ccb90d

commit 8cc96ee4169f631917d048cbaeec14ddf8ccb90d
Author: Aaron Merey <amerey@redhat.com>
Date:   Thu Feb 9 20:35:32 2023 -0500

    gdb/source: Fix open_source_file error handling

    open_source_file relies on errno to communicate the reason for a missing
    source file.

    open_source_file may also call debuginfod_find_source.  It is possible
    for debuginfod_find_source to set errno to a value unrelated to the
    reason for a failed download.

    This can result in bogus error messages being reported as the reason for
    a missing source file.  The following error message should instead be
    "No such file or directory":

      Temporary breakpoint 1, 0x00005555556f4de0 in main ()
      (gdb) list
      Downloading source file
/usr/src/debug/glibc-2.36-8.fc37.x86_64/elf/<built-in>
      1       /usr/src/debug/glibc-2.36-8.fc37.x86_64/elf/<built-in>: Directory
not empty.

    Fix this by having open_source_file return a negative errno if it fails
    to open a source file.  Use this value to generate the error message
    instead of errno.

    Approved-By: Tom Tromey <tom@tromey.com>
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29999

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-02-11  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 14:49 [Bug gdb/29999] New: " simark at simark dot ca
2023-01-13 14:49 ` [Bug gdb/29999] " simark at simark dot ca
2023-01-14  1:07 ` amerey at redhat dot com
2023-01-14  1:14 ` simark at simark dot ca
2023-02-11  2:12 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-11  2:16 ` amerey at redhat dot com

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=bug-29999-4717-gRVJtqcwXX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).