public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/18932] New: list command doesn't work in TUI any more
Date: Mon, 07 Sep 2015 17:02:00 -0000	[thread overview]
Message-ID: <bug-18932-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18932
           Summary: list command doesn't work in TUI any more
           Product: gdb
           Version: 7.10
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: ssbssa at yahoo dot de
  Target Milestone: ---

Before (up to 7.9) the list command updated the source window contents.
Now it returns to the current frame position.

On the other hand the frame command without argument now doesn't move to the
current frame position any more.

I'm pretty sure it started from this commit:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;f=gdb/tui/tui-hooks.c;h=0986c744dfecb8177de90020646090e9ed23cfe7

When setting a breakpoint at tui_before_prompt() you see that the list command
actually does work, but tui_refresh_frame_and_register_information() then
immediately jumps back to the current frame position.

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


             reply	other threads:[~2015-09-07 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 17:02 ssbssa at yahoo dot de [this message]
2015-09-07 17:04 ` [Bug tui/18932] " ssbssa at yahoo dot de

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