public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "magiblot at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/26172] New: Terminal becomes broken when a source file is not found when entering the TUI
Date: Thu, 25 Jun 2020 19:50:18 +0000	[thread overview]
Message-ID: <bug-26172-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26172
           Summary: Terminal becomes broken when a source file is not
                    found when entering the TUI
           Product: gdb
           Version: 9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: magiblot at hotmail dot com
  Target Milestone: ---

Created attachment 12662
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12662&action=edit
Links to recordings showing the issue

Hi,

When entering the TUI mode of gdb, if a source file is not found, in many cases
the terminal session becomes broken: newlines are performed without carriage
return, typed letters do not appear on screen, etc.

Here are some examples:

https://asciinema.org/a/AUHgRdh0zAAJk4oIJ9RZt01A4

https://asciinema.org/a/yLFUCIzI8UoG0TWg0DHAHUQ6R

The last video suggests that this could be caused by source code being missing
for frame #0, regardless of the current frame.

Thanks.

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

             reply	other threads:[~2020-06-25 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 19:50 magiblot at hotmail dot com [this message]
2020-06-26  2:25 ` [Bug tui/26172] " simark at simark dot ca
2020-08-09 18:56 ` tromey at sourceware dot org
2020-09-01 11:08 ` magne.hov at gmail dot com
2020-09-01 14:09 ` tromey at sourceware dot 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-26172-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).