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: gdb_suppress_entire_file must die


On Tue, Feb 04, 2003 at 04:00:17PM -0600, Michael Elizabeth Chastain wrote:
> Well, this does not work as I hoped:
> 
>   if { [gdb_compile ...] != "" } {
>     perror "Testcase compile failed"
>     continue
>   }
> 
> However, I believe that this will:
> 
>   if { [gdb_compile ...] != "" } {
>     perror "Testcase compile failed" 0
>     continue
>   }
> 
> Bet you didn't know that perror can take a second argument!
> 
> It turns out that the ERROR/WARN count is not being reset at the
> end of each file, but it *is* reset at the end of each test.
> The threshold is 1 error or 3 warnings.  After that, exactly one
> test gets forced to UNRESOLVED.
> 
> I don't know where to reset errcnt and warncnt properly in lib/gdb.exp.
> Maybe Daniel J can suggest something?

No idea, sorry.  Using perror that way is probably fine.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


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