bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Marcel Böhme
Dear all, There is another bug that sneaked into the speed patch of seq on 13.09.12: 560   if (all_digits_p (argv[optind]) 561   (n_args == 1 || all_digits_p (argv[optind + 1])) 562   (n_args 3 || STREQ (1, argv[optind + 2])) 563   !equal_width !format_str strlen (separator)

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Pádraig Brady
On 01/22/2013 10:43 AM, Marcel Böhme wrote: Dear all, There is another bug that sneaked into the speed patch of seq on 13.09.12: 560 if (all_digits_p (argv[optind]) 561(n_args == 1 || all_digits_p (argv[optind + 1])) 562(n_args 3 || STREQ (1, argv[optind + 2])) 563

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Pádraig Brady
On 01/22/2013 11:23 AM, Pádraig Brady wrote: On 01/22/2013 10:43 AM, Marcel Böhme wrote: Dear all, There is another bug that sneaked into the speed patch of seq on 13.09.12: 560 if (all_digits_p (argv[optind]) 561(n_args == 1 || all_digits_p (argv[optind + 1])) 562(n_args

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Stefano Lattarini
On 01/22/2013 12:23 PM, Pádraig Brady wrote: On 01/22/2013 10:43 AM, Marcel Böhme wrote: Dear all, There is another bug that sneaked into the speed patch of seq on 13.09.12: 560 if (all_digits_p (argv[optind]) 561(n_args == 1 || all_digits_p (argv[optind + 1])) 562

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Bernhard Voelker
On 01/22/2013 01:17 PM, Pádraig Brady wrote: Updated patch attached. That one is looking good ... but while we're at it: Anyone tried this, i.e. a Zero as INCREMENT? $ seq 1 0 2 This is equal to `yes 0`. Well, this is probably a (not documented) feature, but in the following examples, the 1

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Pádraig Brady
On 01/22/2013 12:17 PM, Pádraig Brady wrote: On 01/22/2013 11:23 AM, Pádraig Brady wrote: On 01/22/2013 10:43 AM, Marcel Böhme wrote: Dear all, There is another bug that sneaked into the speed patch of seq on 13.09.12: 560 if (all_digits_p (argv[optind]) 561(n_args == 1 ||

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Pádraig Brady
On 01/22/2013 12:28 PM, Bernhard Voelker wrote: On 01/22/2013 01:17 PM, Pádraig Brady wrote: Updated patch attached. That one is looking good ... but while we're at it: Anyone tried this, i.e. a Zero as INCREMENT? $ seq 1 0 2 This is equal to `yes 0`. Well, this is probably a (not

bug#13525: 8.20 - [seq 1 3 1] treated as [seq 1 3]

2013-01-22 Thread Bernhard Voelker
On 01/22/2013 02:24 PM, Pádraig Brady wrote: Yes I was wondering that myself. Though I suppose that `seq 0 0 1` prints endlessly, means that it's consistent that as long as start = end and step == 0, then start is printed endlessly. Yes, from a mathematical point of view, seq is right.

bug#13516: tests/rm/unread3 fails on Mac OS X 10.8

2013-01-22 Thread Paul Eggert
On 01/22/13 11:22, Assaf Gordon wrote: 3. Running with 'sudo', 'rm' doesn't fail: $ sudo dtruss $D/rm -r $D/a $D/b 2/tmp/rm_trace.txt You need a sudo inside dtruss, to, right? Something like this sudo dtruss sudo -u $USER $D/rm -r $D/a $D/b 2/tmp/rm_trace.txt

bug#13516: tests/rm/unread3 fails on Mac OS X 10.8

2013-01-22 Thread Assaf Gordon
Paul Eggert wrote, On 01/22/2013 03:21 PM: On 01/22/13 11:22, Assaf Gordon wrote: 3. Running with 'sudo', 'rm' doesn't fail: $ sudo dtruss $D/rm -r $D/a $D/b 2/tmp/rm_trace.txt You need a sudo inside dtruss, to, right? Something like this sudo dtruss sudo -u $USER $D/rm -r $D/a

bug#13530: head: memory exhausted when printing all from stdin but last P/E bytes

2013-01-22 Thread Lei Zhang
Hi All, We found a bug in the `head' program of coreutils 8.20: Invoking `head -c -P' or `head -c -E' will cause memory exhaustion. However, smaller units (e.g., b, K, M) work fine; bigger units (e.g., Z, Y) fail properly (by outputing number of bytes is so large that it is not representable).