Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
	fnasser@redhat.com, Michael Elizabeth Chastain <mec@shout.net>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add "needs_status_wrapper" feature to gdb testsuite.
Date: Thu, 23 May 2002 10:21:00 -0000	[thread overview]
Message-ID: <3CED2183.3B7A@redhat.com> (raw)
In-Reply-To: <3CED1429.9020908@cygnus.com>

Andrew Cagney wrote:
> 
> > This is a feature that has been being used in the GCC testsuite, but I was completely unaware of it before now.
> 
> Michael, this is _still_ broken.

Sorry -- I think there's a fix in-house: I've just been
too busy to push it out to sources.  I'll do it today.


> 
> > This enables tests that look for an exit status to succeed even
> > on targets that don't implement the exit status.  I think it's
> > pretty cool!
> >
> > I've modified two tests from gdb/testsuite to take advantage of it.
> > I'm not sure which other tests may also need modification, but
> > now there are a couple of examples to look at.
> >
> > Index: lib/gdb.exp
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
> > retrieving revision 1.15
> > diff -p -r1.15 gdb.exp
> > *** lib/gdb.exp    3 Apr 2002 16:17:11 -0000    1.15
> > --- lib/gdb.exp    7 May 2002 00:10:06 -0000
> > *************** proc gdb_preprocess {source dest args} {
> > *** 1092,1099 ****
> > --- 1092,1125 ----
> >       return $result;
> >   }
> >   + set gdb_wrapper_initialized 0
> > + + proc gdb_wrapper_init { args } {
> > +     global gdb_wrapper_initialized;
> > +     global gdb_wrapper_file;
> > +     global gdb_wrapper_flags;
> >
> > return;
> >
> > +     if { $gdb_wrapper_initialized == 1 } { return; }
> > + +     if {[target_info exists needs_status_wrapper] && \
> > +         [target_info needs_status_wrapper] != "0" && \
> > +         ![info exists gdb_wrapper_file]} {
> > +     set result [build_wrapper "testglue.o"];
> > +     if { $result != "" } {
> > +         set gdb_wrapper_file [lindex $result 0];
> > +         set gdb_wrapper_flags [lindex $result 1];
> > +     } else {
> > +         warning "Status wrapper failed to build."
> > +     }
> > +     }
> > +     set gdb_wrapper_initialized 1
> > + }
> > +


  reply	other threads:[~2002-05-23 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 17:48 Michael Snyder
2002-05-10 12:51 ` Andrew Cagney
2002-05-23 10:07   ` Andrew Cagney
2002-05-23 10:21     ` Michael Snyder [this message]
2002-05-23 10:25       ` Andrew Cagney

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=3CED2183.3B7A@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --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