public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 06/11] gdb: Use std::string_view instead of gdb::string_view
Date: Mon, 16 Oct 2023 16:06:04 +0100	[thread overview]
Message-ID: <e22cb9fd-d667-4dae-aeff-2ac64a4eda6f@amd.com> (raw)
In-Reply-To: <87il78x49e.fsf@tromey.com>



On 14/10/2023 22:50, Tom Tromey wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> 
> 
>>>>>> "Lancelot" == Lancelot Six <lancelot.six@amd.com> writes:
> 
> Lancelot> Given that GDB now requires a C++17, replace all uses of
> Lancelot> gdb::string_view with std::string_view.
> 
> Lancelot> This change has mostly been done automatically:
> Lancelot> - gdb::string_view -> std::string_view
> Lancelot> - #include "gdbsupport/gdb_string_view.h" -> #include <string_view>
> 
> Lancelot> The implementation and tests of gdb::string_view are unchanged, they will
> Lancelot> be removed in a following patch.
> 
> IIRC there are some spots using gdb::string_view that construct one with
> nullptr, which isn't allowed by std::string_view.  Maybe a test run
> using the libstdc++ debug mode would detect this?
> 
> Tom

Hi,

It looks like libstdc++'s debug mode won't catch this, but this leads to 
a segfault on my system, so I am fairly confident with the testing.

That being said, I went through the patch again. I think one use can be 
a problem (but is not exercised by the testsuite), and one might be 
worth adding an assertion, just in case.  I have added the following 
locally and am extending the commit message.  It will be in a V2, but 
I'll wait for other comment (if any) before sending it.

Best,
Lancelot.

---
diff --git a/gdb/tui/tui-io.c b/gdb/tui/tui-io.c
index 83218dc4797..78bafec38ca 100644
--- a/gdb/tui/tui-io.c
+++ b/gdb/tui/tui-io.c
@@ -1197,7 +1197,10 @@ tui_getc_1 (FILE *fp)
          Compare keyname instead.  */
        if (ch >= KEY_MAX)
         {
-         auto name = std::string_view (keyname (ch));
+         std::string_view name;
+         if (const char *name_str = keyname (ch);
+             name_str != nullptr)
+           name = std::string_view (name_str);

           /* The following sequences are hardcoded in readline as
              well.  */
diff --git a/gdbsupport/format.h b/gdbsupport/format.h
index 5330bbe361e..26e327a60e8 100644
--- a/gdbsupport/format.h
+++ b/gdbsupport/format.h
@@ -56,6 +56,7 @@ struct format_piece
        argclass (argc),
        n_int_args (n)
    {
+    gdb_assert (str != nullptr);
    }

    bool operator== (const format_piece &other) const

  parent reply	other threads:[~2023-10-16 15:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 14:44 [PATCH 00/11] GDB: Require C++17 Lancelot Six
2023-10-13 14:44 ` [PATCH 01/11] gdb/ax_cxx_compile_stdcxx.m4: upgrade Lancelot Six
2023-10-13 14:44 ` [PATCH 02/11] gdb/gdbsupport/gdbserver: Require c++17 Lancelot Six
2023-10-13 15:21   ` Eli Zaretskii
2023-10-16 21:50   ` Pedro Alves
2023-10-13 14:44 ` [PATCH 03/11] gdb: Use C++17's std::make_unique instead of gdb::make_unique Lancelot Six
2023-10-16 19:14   ` Tom Tromey
2023-10-17 14:02     ` Lancelot SIX
2023-10-13 14:44 ` [PATCH 04/11] gdb: Replace gdb::optional with std::optional Lancelot Six
2023-10-13 14:44 ` [PATCH 05/11] gdbsupport: remove gdb::optional Lancelot Six
2023-10-13 14:44 ` [PATCH 06/11] gdb: Use std::string_view instead of gdb::string_view Lancelot Six
2023-10-14 21:50   ` Tom Tromey
2023-10-14 23:58     ` Six, Lancelot
2023-10-16 15:06     ` Lancelot SIX [this message]
2023-10-16 19:35       ` Tom Tromey
2023-10-16 21:51         ` Pedro Alves
2023-10-17 14:13           ` Lancelot SIX
2023-10-17 14:20             ` Simon Marchi
2023-10-13 14:44 ` [PATCH 07/11] gdb: Remove uses of gdb::to_string (const std::string_view &) Lancelot Six
2023-10-13 14:44 ` [PATCH 08/11] gdbsupport: Remove gdb::string_view Lancelot Six
2023-10-16 19:38   ` Tom Tromey
2023-10-13 14:44 ` [PATCH 09/11] gdbsupport: Replace gdb::invoke_result with std::invoke_result Lancelot Six
2023-10-13 14:44 ` [PATCH 10/11] gdb/disasm.h: Mark callbacks noexcept unconditionally Lancelot Six
2023-10-16 21:51   ` Pedro Alves
2023-10-13 14:44 ` [PATCH 11/11] gdb: Use initializers in lambda captures unconditionally Lancelot Six
2023-10-16 19:43 ` [PATCH 00/11] GDB: Require C++17 Tom Tromey
2023-10-16 21:53   ` Pedro Alves
2023-10-23 13:42     ` Lancelot SIX
2023-10-28 20:48       ` Lancelot SIX
2023-11-21 12:04         ` [COMMITTED PATCH v2 0/9] " Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 1/9] gdb: Use C++17's std::make_unique instead of gdb::make_unique Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 2/9] gdb: Replace gdb::optional with std::optional Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 3/9] gdbsupport: remove gdb::optional Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 4/9] gdb: Use std::string_view instead of gdb::string_view Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 5/9] gdb: Remove uses of gdb::to_string (const std::string_view &) Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 6/9] gdbsupport: Remove gdb::string_view Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 7/9] gdbsupport: Replace gdb::invoke_result with std::invoke_result Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 8/9] gdb/disasm.h: Mark callbacks noexcept unconditionally Lancelot Six
2023-11-21 12:05         ` [COMMITTED PATCH v2 9/9] gdb: Use initializers in lambda captures unconditionally Lancelot Six

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=e22cb9fd-d667-4dae-aeff-2ac64a4eda6f@amd.com \
    --to=lancelot.six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --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).