public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30389] New: [gdb/tui] status line string longer than necessary
Date: Tue, 25 Apr 2023 10:43:42 +0000 [thread overview]
Message-ID: <bug-30389-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30389
Bug ID: 30389
Summary: [gdb/tui] status line string longer than necessary
Product: gdb
Version: 13.1
Status: NEW
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider this bit in tui_locator_window::make_status_line ():
...
std::string string_val = string.release ();
if (string.size () < status_size)
string_val.append (status_size - string.size (), ' ');
else if (string.size () > status_size)
string_val.erase (status_size, string.size ());
return string_val;
...
This looks like it's trying to achieve:
...
gdb_assert (string_val.size () == status_size);
...
but that's not the case, because string.size is used instead of
string_val.size.
String.size is 0 for me.
Regression since commit 5d10a2041eb ("gdb: add string_file::release method"),
which did:
...
+ std::string string_val = string.release ();
+
if (string.size () < status_size)
- string.puts (n_spaces (status_size - string.size ()));
+ string_val.append (status_size - string.size (), ' ');
else if (string.size () > status_size)
- string.string ().erase (status_size, string.size ());
+ string_val.erase (status_size, string.size ());
- return std::move (string.string ());
+ return string_val;
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-04-25 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:43 vries at gcc dot gnu.org [this message]
2023-04-25 10:44 ` [Bug tui/30389] " vries at gcc dot gnu.org
2023-04-25 10:52 ` vries at gcc dot gnu.org
2023-04-25 17:56 ` simon.marchi at polymtl dot ca
2023-04-26 16:15 ` cvs-commit at gcc dot gnu.org
2023-04-26 16:19 ` vries at gcc dot gnu.org
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-30389-4717@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).