Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Enable inferior I/O testing for D10V
Date: Tue, 18 Jun 2002 16:24:00 -0000	[thread overview]
Message-ID: <3D0FC133.9040700@cygnus.com> (raw)
In-Reply-To: <200206072357.g57Nv5516938@reddwarf.sfbay.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

> OK to commit?
> 
> (d10v boards and sims are now capable of sending stdout to gdb)
> 
> 2002-06-07  Michael Snyder  <msnyder@redhat.com>
> 
> 	* baseboards/d10v.exp: Inferior I/O no longer needs to be
> 	disabled.
> 
Michael,

the main thing to do is to ensure that the patch is pushed up stream to 
the official maintainer:

dejagnu/
         Send all patches to:
         http://www.gnu.org/software/dejagnu/
         mail:bug-dejagnu@gnu.org
         For changes to the local repostory, send them to
         gdb-patches@sources.redhat.com when generic; and sid@,
         binutils@, gcc@, etc. for sub-components.

Once that is done, the local commit is fine.

Andrew


[-- Attachment #2: mailbox-message://ac131313@movemail/fsf/gdb/patches#22056100 --]
[-- Type: message/rfc822, Size: 3354 bytes --]

From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Enable inferior I/O testing for D10V
Date: Fri, 7 Jun 2002 16:57:05 -0700
Message-ID: <200206072357.g57Nv5516938@reddwarf.sfbay.redhat.com>

OK to commit?

(d10v boards and sims are now capable of sending stdout to gdb)

2002-06-07  Michael Snyder  <msnyder@redhat.com>

	* baseboards/d10v.exp: Inferior I/O no longer needs to be
	disabled.

Index: baseboards/d10v.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/dejagnu/baseboards/d10v.exp,v
retrieving revision 1.13
diff -p -r1.13 d10v.exp
*** d10v.exp	2000/02/17 09:34:20	1.13
--- d10v.exp	2002/06/08 00:09:30
*************** set_board_info noargs  1
*** 40,46 ****
  # And there's no support for signals.
  set_board_info gdb,nosignals  1
  # And it can't do I/O.
! set_board_info gdb,noinferiorio  1
  
  # Used by a few gcc.c-torture testcases to delimit how large the stack can
  # be.
--- 40,46 ----
  # And there's no support for signals.
  set_board_info gdb,nosignals  1
  # And it can't do I/O.
! # set_board_info gdb,noinferiorio  1
  
  # Used by a few gcc.c-torture testcases to delimit how large the stack can
  # be.


  reply	other threads:[~2002-06-18 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 17:12 Michael Snyder
2002-06-18 16:24 ` Andrew Cagney [this message]
2002-06-18 17:46   ` Michael Snyder

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=3D0FC133.9040700@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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