bug-grep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-grep] grep-2.5.1a: "make check" fails on NetBSD/sparc-1.5


From: Stepan Kasal
Subject: Re: [bug-grep] grep-2.5.1a: "make check" fails on NetBSD/sparc-1.5
Date: Fri, 7 Jan 2005 14:36:30 +0100
User-agent: Mutt/1.4.1i

Hello,

On Fri, Jan 07, 2005 at 12:25:20PM +0100, Adrian Bunk wrote:
> > Could you please debug the problem and perhaps write a patch?
> 
> Am I right to assume this was a joke?

well, it wasn't meant as a joke, but I admit it was an unfortunate
formulation.

I, for example, quite enjoy looking for bugs in other projects, but
it's resonable to report them first, because they may have already been
fixed.

I apologize for that unfortunate sentence.
And I'd like to repeat my ``thank you'' for the bug report.  Without
that, I'd have no chance to fix the bug, of course.

> Status: Wrong status code, test \#6 failed
> Status: Wrong status code, test \#7 failed
> FAIL: status.sh

So it seems the compiled grep is not handling -q correctly.
If you are willing to help me with debugging again, could you please 
try the following:

echo abc | src/grep -q a ; echo $?
echo abc | src/grep -q a - ; echo $?
echo abc | src/grep -q a - nonexistent.File ; echo $?
echo abc | src/grep -q a nonexistent.File - ; echo $?

The output should be 0 in all four cases.  The last command prints

        grep: nonexistent.File: No such file or directory

to stderr, but it should then exit with status 0.

In all these examples, grep should exist on the same line.  So if you apply
the tiny patch attached to this mail, grep should say here in all four cases.
Is it the case?

Perhaps some of the developpers on the bug-grep list has access to NetBSD
and can try to debug grep there.

Have a nice day,
        Stepan Kasal

Attachment: grep-here.patch
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]