RFA: handle GDB prompt appearing in command output

Andrew Cagney ac131313@ges.redhat.com
Fri Jul 12 16:24:00 GMT 2002


> Sun Feb  3 19:52:31 2002  Jim Blandy  <jimb@seadog.cygnus.com>
>> 
>> 	* gdb.base/default.exp: Distinguish the GDB prompt as it appears
>> 	in "info set" and "show" output from the true prompt.
>> 
>> Index: gdb/testsuite/gdb.base/default.exp
>> ===================================================================
>> RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/default.exp,v
>> retrieving revision 1.39.56.2
>> diff -c -r1.39.56.2 default.exp
>> *** gdb/testsuite/gdb.base/default.exp	2001/12/20 22:34:38	1.39.56.2
>> --- gdb/testsuite/gdb.base/default.exp	2002/02/04 03:51:57
>> ***************
>> *** 330,336 ****
>>   # FIXME -- needs to match the entire output
>>   # FIXME -- on native solaris 2.8, this test fails due to this line:
>>   #  prompt:  Gdb's prompt is "(gdb) ".^M
>> ! gdb_test "info set" "confirm:  Whether to confirm potentially dangerous operations is o\[a-z\]*..*\[\r\n\]+history filename:  The filename in which to record the command history is .*\[\r\n\]+listsize:  Number of source lines gdb will list by default is 10.*" "info set"
>>   gdb_test "info symbol" "Argument required .address.."
>>   #test info source
>>   gdb_test  "info source" "No current source file..*" "info source"
>> 

Jim,

As a side effect, this patch no longer checks that the order is correct. 
  Is this intentional?  gdb_expect_list might prove a better choice 
since it still enforces the order.

Andrew

-------------- next part --------------
An embedded message was scrubbed...
From: Jim Blandy <jimb@redhat.com>
Subject: Re: RFA: handle GDB prompt appearing in command output
Date: 20 Jun 2002 13:23:22 -0500
Size: 7462
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20020712/75f471a2/attachment.eml>


More information about the Gdb-patches mailing list