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/26205] New: [tui] gdb aborts during winheight command
Date: Sun, 05 Jul 2020 14:20:57 +0000 [thread overview]
Message-ID: <bug-26205-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26205
Bug ID: 26205
Summary: [tui] gdb aborts during winheight command
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test-case gdb.tui/new-layout.exp, I run into:
...
PASS: gdb.tui/new-layout.exp: horizontal display
ERROR: : spawn id exp48 not open
while executing
"expect {
-i exp48 -timeout 10
-re "^\[\x07\x08\x0a\x0d\]" {
scan $expect_out(0,string) %c val
set hexval [format "%02x" $val]
ver..."
("uplevel" body line 1)
invoked from within
"uplevel $body" NONE : spawn id exp48 not open
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)
...
This minimal example already aborts (though I'm not sure this is a correct
minimal representation of the problem described above):
...
$ gdb -tui -ex "winheight src - 5"
...
Aborted (core dumped)
L?? PC: ??
$
...
Backtrace:
...
#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 /home/vries/gdb_versions/devel/src/gdb/tui/tui-win.c:663
#3 0x000000000094a241 in tui_set_win_height_command (arg=0x7fffffffe1d8 "src -
5",
from_tty=1) at /home/vries/gdb_versions/devel/src/gdb/tui/tui-win.c:870
#4 0x00000000004f9abc in do_const_cfunc (c=0x122f470, args=0x7fffffffe1d8 "src
- 5",
from_tty=1) at /home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:95
#5 0x00000000004fd171 in cmd_func (cmd=0x122f470, args=0x7fffffffe1d8 "src -
5", from_tty=1)
at /home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:2181
#6 0x000000000090daf8 in execute_command (p=0x7fffffffe1de "5", from_tty=1)
at /home/vries/gdb_versions/devel/src/gdb/top.c:668
#7 0x000000000073c1c1 in catch_command_errors (
command=0x90d57f <execute_command(char const*, int)>,
arg=0x7fffffffe1ce "winheight src - 5", from_tty=1)
at /home/vries/gdb_versions/devel/src/gdb/main.c:457
#8 0x000000000073d598 in captured_main_1 (context=0x7fffffffdb60)
at /home/vries/gdb_versions/devel/src/gdb/main.c:1218
#9 0x000000000073d78d in captured_main (data=0x7fffffffdb60)
at /home/vries/gdb_versions/devel/src/gdb/main.c:1243
#10 0x000000000073d7f8 in gdb_main (args=0x7fffffffdb60)
at /home/vries/gdb_versions/devel/src/gdb/main.c:1268
#11 0x0000000000413d39 in main (argc=9, argv=0x7fffffffdc68)
at /home/vries/gdb_versions/devel/src/gdb/gdb.c:32
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-07-05 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 14:20 vries at gcc dot gnu.org [this message]
2020-07-05 14:21 ` [Bug tui/26205] " vries at gcc dot gnu.org
2020-07-05 15:54 ` vries at gcc dot gnu.org
2020-07-05 16:07 ` tromey at sourceware dot org
2020-07-05 16:09 ` tromey at sourceware dot org
2020-07-05 21:18 ` vries at gcc dot gnu.org
2020-07-05 21:41 ` vries at gcc dot gnu.org
2020-07-05 21:44 ` vries at gcc dot gnu.org
2020-07-06 7:54 ` cvs-commit at gcc dot gnu.org
2020-07-06 7:57 ` 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-26205-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).