Here's a new copy of this script. I fixed a minor bug where it wasn't reporting
that two blank lines matched due to a problem with GNU expr not being able to
match an empty string. I added some comments too.
Didn't seem worthwhile to generate a patch on something so short yet so I've
included the whole file.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
"The only difference between me and a madman is that I am not mad."
-- Salvador Dali
"Derek R. Price" wrote:
> I thought I was staring at the check.logs from some failed sanity.sh
> runs for way too long before spotting the lines which failed to match.
> Anyway, I wrote this script to solve the problem. It'll take the path
> to a check.log as an argument and tell you what's wrong with one of the
> patterns in it. It prints mismatched lines on top of each other too,
> which usually makes them much easier to scan. Pass in -a if you want it
> to try and match against the alternate pattern.
>
> I banged on it a bit and it seems to be reliable.
>
> Derek
>
> --
> Derek Price CVS Solutions Architect ( http://CVSHome.org )
> mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
> --
> He who laughs last thinks slowest.
debug.check.log.sh
