public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tankut.baris.aktemur at intel dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/28833] New: Ctrl-D distorts GDB prompt
Date: Fri, 28 Jan 2022 09:32:04 +0000	[thread overview]
Message-ID: <bug-28833-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28833
           Summary: Ctrl-D distorts GDB prompt
           Product: gdb
           Version: 11.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: tankut.baris.aktemur at intel dot com
  Target Milestone: ---

With GDB-10, Ctrl-D quits GDB with the following output:

  $ gdb-10 -q
  (gdb) quit

But with GDB-11 or with the current upstream, the prompt is distorted.
Start GDB-11:

  $ gdb-11 -q
  (gdb)

and now hit Ctrl-D:

  quit)
  $

This seems like a regression.

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

             reply	other threads:[~2022-01-28  9:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  9:32 tankut.baris.aktemur at intel dot com [this message]
2022-01-28  9:34 ` [Bug cli/28833] " tankut.baris.aktemur at intel dot com
2022-01-28  9:36 ` tankut.baris.aktemur at intel dot com
2022-01-28 16:07 ` tromey at sourceware dot org
2022-02-06 12:14 ` aburgess at redhat dot com
2022-02-07 10:28 ` tankut.baris.aktemur at intel dot com
2022-02-08 10:15 ` aburgess at redhat dot com
2022-02-14 12:14 ` blarsen at redhat dot com
2022-02-15 11:48 ` aburgess at redhat dot com
2022-02-15 12:34 ` schwab@linux-m68k.org
2022-02-15 14:01 ` aburgess at redhat dot com
2022-02-16 17:06 ` aburgess at redhat dot com
2022-02-17  7:01 ` tankut.baris.aktemur at intel dot com
2022-02-27 11:21 ` brobecker at gnat dot com
2022-03-06 10:05 ` brobecker at gnat dot com
2022-03-07 15:14 ` aburgess at redhat dot com
2022-03-16 20:44 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:53 ` aburgess at redhat dot com

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-28833-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).