public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Merey <amerey@redhat.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, keiths@redhat.com, Aaron Merey <amerey@redhat.com>
Subject: [PATCH v2 0/2] gdb: Fix open_source_file error handling
Date: Thu,  9 Feb 2023 20:59:40 -0500	[thread overview]
Message-ID: <20230210015942.3180401-1-amerey@redhat.com> (raw)

v1: https://sourceware.org/pipermail/gdb-patches/2023-February/196529.html

v2 implements the following suggestions:
https://sourceware.org/pipermail/gdb-patches/2023-February/196693.html

Aaron Merey (2):
  Move implementation of perror_with_name to gdbsupport
  gdb/source: Fix open_source_file error handling

 gdb/debuginfod-support.h | 15 +++++++++------
 gdb/source-cache.c       |  2 +-
 gdb/source.c             | 40 ++++++++++++++++++++++++++++++----------
 gdb/source.h             |  5 +++--
 gdb/utils.c              | 36 ------------------------------------
 gdbserver/utils.cc       | 22 ----------------------
 gdbsupport/errors.cc     | 24 ++++++++++++++++++++++++
 gdbsupport/errors.h      | 13 ++++++++++---
 8 files changed, 77 insertions(+), 80 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-02-10  2:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  1:59 Aaron Merey [this message]
2023-02-10  1:59 ` [PATCH 1/2] Move implementation of perror_with_name to gdbsupport Aaron Merey
2023-02-10 14:39   ` Tom Tromey
2023-02-11  2:13     ` Aaron Merey
2023-02-10  1:59 ` [PATCH 2/2] gdb/source: Fix open_source_file error handling Aaron Merey
2023-02-10 14:41   ` Tom Tromey
2023-02-11  2:14     ` Aaron Merey

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=20230210015942.3180401-1-amerey@redhat.com \
    --to=amerey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tom@tromey.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).