GNU bug report logs - #18949
Possible BUG in binary SEQ (1) / Bringing SEQ into endless loop.

Previous Next

Package: coreutils;

Reported by: Philippe Rassek <philipperassek <at> gmx.de>

Date: Tue, 4 Nov 2014 22:40:01 UTC

Severity: normal

Tags: fixed

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18949 in the body.
You can then email your comments to 18949 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-coreutils <at> gnu.org:
bug#18949; Package coreutils. (Tue, 04 Nov 2014 22:40:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Philippe Rassek <philipperassek <at> gmx.de>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Tue, 04 Nov 2014 22:40:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Philippe Rassek <philipperassek <at> gmx.de>
To: bug-coreutils <at> gnu.org
Subject: Possible BUG in binary SEQ (1) / Bringing SEQ into endless loop.
Date: Tue, 4 Nov 2014 23:19:57 +0100

Dear Sirs,

when running for example seq 1 0 10 it will go into an endless loop.

Imho the 2nd parameter (Increment Statement) should be checked for > 0
(greater then 0) before executing.

Cheers

Philippe Rassek
Information forwarded to bug-coreutils <at> gnu.org:
bug#18949; Package coreutils. (Fri, 19 Oct 2018 01:04:02 GMT) Full text and rfc822 format available.

Message #8 received at 18949 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: 18949 <at> debbugs.gnu.org
Date: Thu, 18 Oct 2018 19:02:56 -0600

tags 18949 fixed
close 18949
stop

(triaging old bugs)

Hello,

Philippe Rassek wrote:
> when running for example seq 1 0 10 it will go into an endless loop.
> 
> Imho the 2nd parameter (Increment Statement) should be checked for >
> 0 (greater then 0) before executing.
It seems your email "fell between the cracks" and not replied to in many 
years. Sorry about that.

You suggested have been implemented some time ago, here:

https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=81e589021d9c47e4fbc4284e82881a9703246476

As such, I'm marking this as "fixed" and closing.

regards,
 - assaf
Added tag(s) fixed. Request was from Assaf Gordon <assafgordon <at> gmail.com> to control <at> debbugs.gnu.org. (Fri, 19 Oct 2018 01:04:02 GMT) Full text and rfc822 format available.
bug closed, send any further explanations to 18949 <at> debbugs.gnu.org and Philippe Rassek <philipperassek <at> gmx.de> Request was from Assaf Gordon <assafgordon <at> gmail.com> to control <at> debbugs.gnu.org. (Fri, 19 Oct 2018 01:04:03 GMT) Full text and rfc822 format available.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 16 Nov 2018 12:24:06 GMT) Full text and rfc822 format available.
This bug report was last modified 6 years and 301 days ago.

Previous Next

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