This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Testsuite for avr-as
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Erik Christiansen <erik at dd dot nec dot com dot au>
- Cc: binutils at sources dot redhat dot com
- Date: Thu, 20 Jan 2005 07:59:42 -0500 (EST)
- Subject: Re: Testsuite for avr-as
- References: <20041207003334.GB732@dd.nec.com.au> <Pine.BSF.4.58.0412062000000.65411@dair.pair.com><20041207042355.GC732@dd.nec.com.au> <Pine.BSF.4.58.0412070753180.84449@dair.pair.com><20041209062044.GB764@dd.nec.com.au> <Pine.BSF.4.58.0412090608080.1201@dair.pair.com><20041210063526.GA752@dd.nec.com.au> <Pine.BSF.4.58.0412100638550.51021@dair.pair.com><20050120055249.GC929@dd.nec.com.au>
On Thu, 20 Jan 2005, Erik Christiansen wrote:
> After eliminating errors due to incomplete "regexification" of the new
> opcode.d file, gas.log still reports "UNRESOLVED: opcode". No problem,
> adding "set verbose 1" elucidates to this extent:
Usually you add one "-v" for each verbosity level to
RUNTESTFLAGS on the command line to the same effect.
> Error/Warning threshold exceeded: 1 0 (max. 1 3)
>
> And "set verbose 3" additionally lists the regex/line pairs tested.
> _But_, at no point is the error shown in the log. Is there a known way
> to induce DejaGnu to reveal the "Error/Warning" that it claims to have
> detected?
I don't know, I don't recognize the error you mention. If you
use run_dump_test, the lines that differ and the expected
pattern are shown in the log. But it seems this is not what you
see, but some other error?
I suggest you send your testsuite patches to the list.
Maybe it's a bug in one of the regexps in the test.
brgds, H-P