Package: coreutils
Version: 5.97-5.3
Severity: normal

I observed seq to do strange things when FIRST and LAST are equal and very big 
and INCREMENT is very small.

The case FIRST=LAST is very unusual, thus I set the severity of this big to 
normal.
I observed the Problem while using seq in a script, in which this unusual 
situation occurs sometimes.

As I don't know exactly what is going wrong all I can provide is an example:

$ seq 100 1 100
100
$ seq 1000 1 1000
1000
$ seq 10000 1 10000
10000
[...]
$ seq 1000000000000000000 1 1000000000000000000
1e+18
$ seq 10000000000000000000 1 10000000000000000000
1e+19
$ seq 100000000000000000000 1 100000000000000000000
1e+20
1e+20
1e+20
1e+20
1e+20
$ seq 100000000000000000000 2 100000000000000000000
1e+20
1e+20
1e+20
$ seq 100000000000000000000 3 100000000000000000000
1e+20
1e+20
$ seq 100000000000000000000 4 100000000000000000000
1e+20
1e+20
$ seq 100000000000000000000 5 100000000000000000000
1e+20

As you can see, as soon as FIST and LAST reach 1e+20 seq is printing the 
correct output, but is does it multiple times. Surprisingly, increasing the 
INCREMENT value reduces the number of times seq prints the output until for 
INCREMENT>4 everything works as expected.

I don't know if it is worth fixing this behaviour as it occurs only under very 
rare circumstances, but at least a hint in the man page of seq would be 
desirable. 


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (800, 'testing'), (70, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages coreutils depends on:
ii  libacl1                      2.2.45-1    Access control list shared library
ii  libc6                        2.7-6       GNU C Library: Shared libraries
ii  libselinux1                  2.0.15-2+b1 SELinux shared libraries

coreutils recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to