Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] An initial patch for PR/1961
Date: Wed, 06 Jul 2005 07:50:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0507061508570.13408@wks190384wss.cn.ibm.com> (raw)
In-Reply-To: <20050703191243.GL13811@nevyn.them.org>

On Sun, 3 Jul 2005, Daniel Jacobowitz wrote:

> On Sun, Jun 19, 2005 at 12:02:14AM +0800, Wu Zhou wrote:
> > Hello all,
> > 
> > I did some initial analysis against PR/1961 (Pls add a test for command 
> > input of "-(" ).  I found this SEGV error will also pop when issuing "+)", 
> > "<)", ">(" and so on under gdbtui. 
> > 
> > My intial patch is attached as follows.  Please review.  Thanks.
> > 
> > 2005-06-20  Wu Zhou  <woodzltc@cn.ibm.com>
> > 
> > 	* tui/tui-win.c (parse_scrolling_args): Fix SEGV error with invalid
> > 	scroll command.
> 
> Please update the copyright year in this file.  Otherwise, this patch
> is OK.  Thanks!

Copyright year is updated and patch committed.

BTW.  I ever thought of adding a testcase to verify this, but found that 
gdb will timeout while waiting for the tui output under expect's control.
Is there any method to work around this?  More generally, is there any way 
to test TUI interface using expect? (I don't find any tests for TUI under 
the testsuite directory.)  Maybe it is desirable for TUI to receive enough 
test just like what MI had done. 

Just my two cents anyway.  Comments are highly appreciated.

Cheers
- Wu Zhou


      reply	other threads:[~2005-07-06  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20  1:56 Wu Zhou
2005-07-03 19:12 ` Daniel Jacobowitz
2005-07-06  7:50   ` Wu Zhou [this message]

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=Pine.LNX.4.63.0507061508570.13408@wks190384wss.cn.ibm.com \
    --to=woodzltc@cn.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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