Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/Testsuite] help.exp
Date: Tue, 23 Apr 2002 16:49:00 -0000	[thread overview]
Message-ID: <15557.62199.969948.504263@localhost.redhat.com> (raw)
In-Reply-To: <3CC5EFE0.9D322C64@redhat.com>

Fernando Nasser writes:
 > Elena Zannoni wrote:
 > > 
 > > The recent changes to help.exp eliminating the wildcards introduced a few
 > > failures on the powerpc.
 > > 
 > > How about this to deal with the difference in output for the powerpc
 > > vs. other targets?
 > > 
 > > Elena
 > > 
 > Hi Elena,
 > 
 > I would rather have a '.*' in there instead of the test for a specific
 > target.
 > 

That is the way it was originally. That works fine with the powerpc.

 > You don't need to resubmit: just add the '.*' and post the final
 > version.
 > 

OK.

 > Regards,
 > Fernando
 > 
 > 
 > > 2002-04-23  Elena Zannoni  <ezannoni@redhat.com>
 > > 
 > >         * gdb.base/help.exp: Change 'help status' to allow for PowerPC
 > >         differences.
 > > 
 > > Index: help.exp
 > > ===================================================================
 > > RCS file: /cvs/uberbaum/gdb/testsuite/gdb.base/help.exp,v
 > > retrieving revision 1.10
 > > diff -u -p -r1.10 help.exp
 > > --- help.exp    29 Mar 2002 01:19:11 -0000      1.10
 > > +++ help.exp    23 Apr 2002 23:04:23 -0000
 > > @@ -535,7 +535,13 @@ gdb_test "help source" "Read commands fr
 > >  # test help stack
 > >  gdb_test "help stack" "Examining the stack\..*\[\r\n\]+When the program being debugged stops, gdb selects the innermost frame\.\[\r\n\]+The commands below can be used to select other frames by number or address\.\[\r\n\]+List of commands:\[\r\n\]+backtrace -- Print backtrace of all stack frames\[\r\n\]+bt -- Print backtrace of all stack frames\[\r\n\]+down -- Select and print stack frame called by this one\[\r\n\]+frame -- Select and print a stack frame\[\r\n\]+return -- Make selected stack frame return to its caller\[\r\n\]+select-frame -- Select a stack frame without printing anything\[\r\n\]+up -- Select and print stack frame that called this one\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help stack"
 > >  # test help status
 > > -gdb_test "help status" "Status inquiries\.\[\r\n\]+List of commands:\[\r\n\]+info -- Generic command for showing things about the program being debugged\[\r\n\]+show -- Generic command for showing things about the debugger\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help status"
 > > +
 > > +if [istarget "powerpc-*-*"] then {
 > > +    gdb_test "help status" "Status inquiries\.\[\r\n\]+List of commands:\[\r\n\]+info -- Generic command for showing things about the program being debugged\[\r\n\]+info powerpc -- Various POWERPC info specific commands\[\r\n\]+info powerpc altivec -- Display the contents of the AltiVec registers\[\r\n\]+show -- Generic command for showing things about the debugger\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help status"
 > > +} else {
 > > +    gdb_test "help status" "Status inquiries\.\[\r\n\]+List of commands:\[\r\n\]+info -- Generic command for showing things about the program being debugged\[\r\n\]+show -- Generic command for showing things about the debugger\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help status"
 > > +}
 > > +
 > >  # test help support
 > >  # FIXME -- Ultrix hangs randomly on this very long output from gdb and
 > >  # continues with its output only if something is sent to gdb.
 > 
 > -- 
 > Fernando Nasser
 > Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
 > 2323 Yonge Street, Suite #300
 > Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-04-23 23:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 16:06 Elena Zannoni
2002-04-23 16:35 ` Michael Snyder
2002-04-23 16:47   ` Fernando Nasser
2002-04-23 16:51     ` Elena Zannoni
2002-04-23 17:23       ` Michael Snyder
2002-04-23 20:07         ` Elena Zannoni
2002-04-23 16:39 ` Fernando Nasser
2002-04-23 16:49   ` Elena Zannoni [this message]
2002-04-23 20:55 Michael Elizabeth Chastain
2002-04-23 20:57 ` Elena Zannoni
2002-04-23 21:04 Michael Elizabeth Chastain

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=15557.62199.969948.504263@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=fnasser@redhat.com \
    --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