Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: gdb-patches <gdb-patches@sourceware.org>,
	Pedro Alves <palves@redhat.com>
Subject: [patch 0/3] fix some gdb.base/paginate-bg-execution.exp problems
Date: Fri, 18 Dec 2015 19:23:00 -0000	[thread overview]
Message-ID: <56745D29.504@codesourcery.com> (raw)

This series of patches fixes some problems I ran into testing 
gdb.base/paginate-bg-execution.exp on a remote Windows host via ssh -T 
(that is, no TTY).

Part 1 is the fix previously suggested by Pedro here:
https://sourceware.org/ml/gdb-patches/2015-09/msg00637.html

Part 2 is another fix to the pagination code, and part 3 fixes a think-o 
in the test .exp file itself.

The results for this test with these patches look better, but I'm still 
getting some pattern match failures due to too many end-of-line \r 
characters in the output.  I still need to investigate that; I think we 
have a patch on our local branch that's preventing those extra 
characters from being generated, but I'm seeing different failures there 
instead.  :-S  Anyway, I think that is separate from the pagination/TTY 
issues, so I'd like to get the fixes I have in, at least.

-Sandra


             reply	other threads:[~2015-12-18 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 19:23 Sandra Loosemore [this message]
2015-12-18 19:31 ` [patch 1/3] make prompt_for_continue call throw_quit directly Sandra Loosemore
2015-12-18 19:34   ` Pedro Alves
2015-12-18 19:44 ` [patch 2/3] reset pagination counts even when stdin is not a tty Sandra Loosemore
2015-12-18 20:17   ` Pedro Alves
2015-12-18 19:50 ` [patch 3/3] add missing gdb_test arguments in paginate-bg-execution.exp Sandra Loosemore
2015-12-18 20:40   ` Pedro Alves
2015-12-18 23:49     ` Sandra Loosemore
2015-12-21 11:53       ` Pedro Alves
2015-12-21 12:27         ` Joel Brobecker
2015-12-25 19:39           ` Sandra Loosemore

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=56745D29.504@codesourcery.com \
    --to=sandra@codesourcery.com \
    --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