Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb/tui,c++17] Fix NULL string_view in tui_partial_win_by_name
Date: Sun, 5 Jul 2020 22:47:36 -0400	[thread overview]
Message-ID: <5561a801-080e-72cb-8350-36d3e0aadf7f@simark.ca> (raw)
In-Reply-To: <20200705214048.GA21240@delia>

On 2020-07-05 5:40 p.m., Tom de Vries wrote:
> Hi,
> 
> When building gdb with CFLAGS=-std=gnu17 and CXXFLAGS=-std=gnu++17 and running
> test-case gdb.tui/new-layout.exp, we run into:
> ...
> UNRESOLVED: gdb.tui/new-layout.exp: left window box after shrink (ll corner)
> FAIL: gdb.tui/new-layout.exp: right window box after shrink (ll corner)
> ...
> 
> In a minimal form, we run into an abort when issuing a winheight command:
> ...
> $ gdb -tui -ex "winheight src - 5"
>    <tui stuff>
> Aborted (core dumped)
> $
> ...
> with this backtrace at the abort:
> ...
> \#0  0x0000000000438db0 in std::char_traits<char>::length (__s=0x0)
>      at /usr/include/c++/9/bits/char_traits.h:335
> \#1  0x000000000043b72e in std::basic_string_view<char, \
>    std::char_traits<char> >::basic_string_view (this=0x7fffffffd4f0, \
>    __str=0x0) at /usr/include/c++/9/string_view:124
> \#2  0x000000000094971b in tui_partial_win_by_name (name="src")
>      at src/gdb/tui/tui-win.c:663
> ...
> due to a NULL comparison which constructs a string_view object from NULL:
> ...
>    657  /* Answer the window represented by name.  */
>    658  static struct tui_win_info *
>    659  tui_partial_win_by_name (gdb::string_view name)
>    660  {
>    661    struct tui_win_info *best = nullptr;
>    662
>    663    if (name != NULL)
> ...
> 
> In gdbsupport/gdb_string_view.h, we either use:
> - gdb's copy of libstdc++-v3/include/experimental/string_view, or
> - the standard implementation of string_view, when built with C++17 or later
>   (which in gcc's case comes from libstdc++-v3/include/std/string_view)
> 
> In the first case, there's support for constructing a string_view from a NULL
> pointer:
> ...
>       /*constexpr*/ basic_string_view(const _CharT* __str)
>       : _M_len{__str == nullptr ? 0 : traits_type::length(__str)},
>         _M_str{__str}
>       { }
> ...
> but in the second case, there's not:
> ...
>       __attribute__((__nonnull__)) constexpr
>       basic_string_view(const _CharT* __str) noexcept
>       : _M_len{traits_type::length(__str)},
>         _M_str{__str}
>       { }
> ...
> 
> Fix this by removing the NULL comparison altogether.
> 
> Build on x86_64-linux with CFLAGS=-std=gnu17 and CXXFLAGS=-std=gnu++17, and
> tested.
> 
> Any comments?

This is the second string_view problem in a short amount of time, the other being:

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

When importing the string_view support, I ended up copying experimental/string_view
(which is a version from before it was a standard) from libstdc++, rather than
std/string_view.  In this message:

  https://sourceware.org/legacy-ml/gdb-patches/2018-04/msg00111.html

I said it was because "it is easier to adapt to the c++ standard we follow", but I
don't remember the specific reason.  I think we should change our string_view to
be an adapted copy of std/string_view instead, to minimize the chances of differences
with the standard version.  I started to do it the other day (but did not finish
adapting the tests), and didn't see any blocker.

I still think your patch is good (it would be necessary in any case).

Simon


  parent reply	other threads:[~2020-07-06  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 21:40 Tom de Vries
2020-07-06  2:27 ` Tom Tromey
2020-07-06  2:47 ` Simon Marchi [this message]
2020-07-06  9:19   ` Tom de Vries

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=5561a801-080e-72cb-8350-36d3e0aadf7f@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --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