Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 Joel Brobecker <brobecker@adacore.com>,
	 gdb-patches@sourceware.org
Subject: Re: GDB 8.2.90 available for testing
Date: Thu, 07 Mar 2019 22:44:00 -0000	[thread overview]
Message-ID: <87k1hae23l.fsf@tromey.com> (raw)
In-Reply-To: <a1b789a8-160c-824f-592a-f7b59c7072ff@redhat.com> (Pedro Alves's	message of "Fri, 1 Mar 2019 16:35:02 +0000")

Pedro> #1 - Run a program to main, so that the source window displays the source.
  
Pedro>   a) Press the "up" key.  That manages to actually move the cursor to the line above.
  
I could not reproduce this.

Some of the odd behavior I do see seems to predate any of these changes.
With the system gdb on Fedora 28 and 29 I can:

(gdb) tui enable
(gdb) print 23
$1 = 23
(gdb) ... press Enter a a few times

Here the subsequent prompts aren't seen and the output just looks like

$2 = 23
$3 = 23
...

With git master this is worse and the output looks like:

(gdb) print 23
$1 = 23
(gdb) 
(gdb) $2 = 23

(gdb) $3 = 23

(gdb) $4 = 23


This I tracked down to the "nonl" patch.
I haven't yet debugged that one seriously.

Pedro> #3 - Start gdb with a program, and enable the TUI.  The source window
Pedro>      displays "No Source Available".  Now type "list" in the TUI console.
Pedro>      I just tried it now, and the first time, it printed the source name in
Pedro>      the console window and didn't update/display the source in the source window.
Pedro>      The second time, it displayed the source in the source window, and the third
Pedro>      time it crashed GDB with an uncaught exception:

I will look into the crash, but note that the "list" command is pretty
broken in the TUI.

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

So it isn't super surprising to me that it doesn't work correctly in all
cases.

Tom


  parent reply	other threads:[~2019-03-07 22:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  5:51 Joel Brobecker
2019-02-27 22:05 ` Jim Wilson
2019-03-04 11:15   ` Andrew Burgess
2019-03-04 13:57     ` Alan Hayward
2019-03-04 20:00     ` Jim Wilson
2019-02-28 18:31 ` MinGW build of GDB 8.2.90 (was: GDB 8.2.90 available for testing) Eli Zaretskii
2019-02-28 18:55   ` MinGW build of GDB 8.2.90 Sergio Durigan Junior
2019-02-28 19:06     ` LRN
2019-02-28 19:45     ` Eli Zaretskii
2019-02-28 20:17       ` Sergio Durigan Junior
2019-02-28 20:29         ` Eli Zaretskii
2019-02-28 20:37           ` Sergio Durigan Junior
2019-02-28 18:34 ` GDB 8.2.90 available for testing Eli Zaretskii
2019-03-01 16:35   ` Pedro Alves
2019-03-01 18:50     ` Tom Tromey
2019-03-07 22:44     ` Tom Tromey [this message]
2019-03-08  7:46       ` Eli Zaretskii
2019-03-08 20:57         ` Tom Tromey
2019-03-09  6:13           ` Eli Zaretskii
2019-03-14 17:32             ` Tom Tromey
2019-03-14 19:49               ` Eli Zaretskii
2019-03-15 12:55                 ` Tom Tromey
2019-03-17 15:56               ` Eli Zaretskii
2019-03-17 17:31                 ` Tom Tromey
2019-03-17 18:36                   ` Eli Zaretskii
2019-03-18 14:13                     ` Tom Tromey
2019-03-18 18:08                       ` Eli Zaretskii
2019-03-07 17:42 ` Pedro Franco de Carvalho
     [not found]   ` <4d855905-32ce-ba4b-72f5-037f1796b37e@redhat.com>
2019-03-22 14:42     ` [PATCH] Fix testsuite hangs when gdb_test_multiple body errors out (Re: GDB 8.2.90 available for testing) Simon Marchi
2019-03-25 13:23       ` Pedro Alves
2019-03-22 20:44     ` Pedro Franco de Carvalho
2019-03-25 13:21       ` Pedro Alves
2019-03-25 19:43         ` Pedro Franco de Carvalho
2019-03-26 18:58           ` Pedro Alves
2019-03-26 21:01             ` Pedro Franco de Carvalho
2019-03-28 17:36               ` Joel Brobecker

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=87k1hae23l.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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