GNU bug report logs - #33817
dejagnu(1) fails to find commands specified with spaces and no arguments

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: jcb62281 <at> gmail.com
Subject: bug#33817: closed ()
Date: Fri, 21 Dec 2018 09:10:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#33817: dejagnu(1) fails to find commands specified with spaces and no arguments

which was filed against the dejagnu package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 33817 <at> debbugs.gnu.org.

-- 
33817: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33817
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: bje <at> air.net.au (Ben Elliston)
To: 33817-done <at> debbugs.gnu.org
Date: Fri, 21 Dec 2018 20:08:54 +1100 (AEDT)

Fixed in master.

[Message part 3 (message/rfc822, inline)]

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: bug-dejagnu <at> gnu.org
Subject: dejagnu(1) fails to find commands specified with spaces and no
 arguments
Date: Fri, 21 Dec 2018 00:06:23 -0600

The supplemental patch that fixed erroneous use of "shift" in dejagnu(1) 
also introduced a bug.  (I knew there was a reason I had removed that 
previously.)  The dejagnu(1) launcher is supposed to treat "multi-word 
command" as equivalent to "multi-word-command", but at present will 
(incorrectly) fail to find the command if the former form is used 
without other arguments.  The testsuite misses this bug because (oops) 
all of the command tests use verbose mode.

I already have a patch to fix this; I am writing this because I want a 
bug number to put in the testcase, and I think that this list is tied 
into a debbugs instance now.  :-)


-- Jacob

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.