public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/15933] TUI shows registers of the wrong frame the first time Date: Thu, 05 Sep 2013 11:20:00 -0000 [thread overview] Message-ID: <bug-15933-4717-b5Yn1kwFNI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15933-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15933 --- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- CVSROOT: /cvs/src Module name: src Changes by: palves@sourceware.org 2013-09-05 11:20:16 Modified files: gdb : ChangeLog gdb/tui : tui-regs.c Log message: [PR tui/15933] TUI shows registers of the wrong frame the first time I've stumbled on this by inspection. When the TUI's register window is first displayed, it always shows the registers of the current frame, instead of of the selected frame, which is obviously bogus. E.g., (gdb) step # into "function" (gdb) up (gdb) tui reg general # or C-x 2, C-x 2 shows the registers of "function", rather than the caller's. A subsequent: (gdb) frame or (gdb) down (gdb) up can be used as workaround to "fix" it. gdb/ 2013-09-05 Pedro Alves <palves@redhat.com> PR tui/15933 * tui/tui-regs.c (tui_show_registers): Show registers of the selected frame, not the current frame. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15973&r2=1.15974 http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tui/tui-regs.c.diff?cvsroot=src&r1=1.50&r2=1.51 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-09-05 11:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-05 11:09 [Bug tui/15933] New: " palves at redhat dot com 2013-09-05 11:09 ` [Bug tui/15933] " palves at redhat dot com 2013-09-05 11:20 ` cvs-commit at gcc dot gnu.org [this message] 2013-09-05 11:50 ` palves 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-15933-4717-b5Yn1kwFNI@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: linkBe 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).