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/27680] New: ui-style.c:243: internal-error: bool ui_file_style::parse(const char*, size_t*): Assertion `match == 0' failed.'
Date: Thu, 01 Apr 2021 09:09:03 +0000	[thread overview]
Message-ID: <bug-27680-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27680
           Summary: ui-style.c:243: internal-error: bool
                    ui_file_style::parse(const char*, size_t*): Assertion
                    `match == 0' failed.'
           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: ---

On openSUSE tumbleweed I'm running into a cluster of tui fails:
...
FAIL: gdb.tui/basic.exp: asm window shows main
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/basic.exp: source box in split layout (ll corner)
FAIL: gdb.tui/basic.exp: asm box in split layout (ul corner)
FAIL: gdb.tui/list.exp: asm window shows main
ERROR: invalid command name "_csi_L"
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/list.exp: source is still visible
FAIL: gdb.tui/new-layout.exp: example layout shows assembly
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/new-layout.exp: right window box (ul corner)
FAIL: gdb.tui/new-layout.exp: horizontal display
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/new-layout.exp: right window box after shrink (ul corner)
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/new-layout.exp: right window box after grow (ul corner)
FAIL: gdb.tui/tui-layout-asm-short-prog.exp: check asm box contents
ERROR: invalid command name "_csi_L"
ERROR: invalid command name "_csi_L"
FAIL: gdb.tui/tui-layout-asm.exp: check asm box contents
...

The first FAIL happens after we hit:
...
+++ Inserted string '+', cursor: (14, 79) -> (15, 0)
+++ wait_for: _csi_G <<<80>>>
+++ Cursor Horizontal Absolute (80), cursor: (15, 0) -> (15, 79)
+++ wait_for: _csi_m <<<39>>>
+++ Select Graphic Rendition (39), cursor: (15, 79) -> (15, 79)
+++ wait_for: _csi_m <<<0;10>>>
+++ Select Graphic Rendition (0, 10), cursor: (15, 79) -> (15, 79)
^[[H^[[0;10;1m^[[36m+-^[[77b+|^[[80G||^[[80G||^[[80G||^[[80G||^[[80G||^[[80G||^[[80G||^[\
[80G||^[[80G||^[[80G||^[[80G||^[[80G||^[[80G|+-^[[77b+^[[B^[[39m^[[0;10m^[[19d/data/gdb_versions/devel/src/gdb/ui-style.c:243:
internal-error: bool ui_file_style::parse(const char*, size_t*): Assertion
`match == 0' failed.^M^[[BA problem internal to GDB has been
detected,^M^[[Bfurther debugging may prove unreliable.^M^[[BQuit this debugging
session? (y or n) +++ wait_for: _csi_H <<<>>>
+++ Cursor Position (1, 1), cursor: (15, 79) -> (0, 0)
+++ wait_for: _csi_m <<<0;10;1>>>
+++ Select Graphic Rendition (0, 10, 1), cursor: (0, 0) -> (0, 0)
+++ wait_for: _csi_m <<<36>>>
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-04-01  9:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  9:09 vries at gcc dot gnu.org [this message]
2021-04-01  9:12 ` [Bug tui/27680] " vries at gcc dot gnu.org
2021-04-01  9:13 ` vries at gcc dot gnu.org
2021-04-01  9:20 ` vries at gcc dot gnu.org
2021-04-01  9:26 ` vries at gcc dot gnu.org
2021-04-01  9:27 ` vries at gcc dot gnu.org
2021-04-01  9:43 ` vries at gcc dot gnu.org
2021-04-01 12:55 ` tromey at sourceware dot org
2021-04-01 13:44 ` vries at gcc dot gnu.org
2021-04-01 13:49 ` tromey at sourceware dot org
2021-04-06  8:40 ` cvs-commit at gcc dot gnu.org
2021-04-06  8:42 ` vries at gcc dot gnu.org
2021-05-01 11:00 ` stefan.bruens@rwth-aachen.de
2021-05-03  7:57 ` vries at gcc dot gnu.org
2021-05-03 12:48 ` vries at gcc dot gnu.org
2021-05-05 21:13 ` 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-27680-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).