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

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!

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-07-03 19:12 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 [this message]
2005-07-06  7:50   ` Wu Zhou

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=20050703191243.GL13811@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.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