This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Extracting testsuite log


Jason R Thorpe writes:
 > I'm finally getting back to working on multi-arch'ing the alpha target,
 > and have some questions about using the testsuite effectively...
 > 
 > I'm getting a bunch of testsuite failures (though, certainly fewer
 > than before multi-arch'ing), and I'd like to track them down.
 > 
 > However, when I mimmick the test by hand, it seems to return the results
 > that the testsuite is expecting.  For example:
 > 
 > FAIL: gdb.base/callfuncs.exp: bt after continuing from call dummy breakpoint
 > FAIL: gdb.base/callfuncs.exp: bt after finishing from call dummy breakpoint
 > 
 > When I mimmick that test by-hand, it seems to work fine.
 > 
 > What I'd like to do is see the exact output that expect saw when running
 > the test.  Is there an easy way to do this?
 > 
 > -- 
 >         -- Jason R. Thorpe <thorpej@wasabisystems.com>

yes, I usually add:
 
exp_internal 1
[...]
exp_internal 0

in the .exp file around the part that I want to monitor.  It will
print all the output that expect is trying to match and a  'yes' or 'no'
for each case.

Elena


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]