Christopher Faylor wrote:
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
Reproduced on several machines. I wonder what can it be.
Just try running 'time' from the bash prompt. You get a SEGV
Krzysztof Duleba wrote:
Christopher Faylor wrote:
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
Reproduced on several machines. I wonder what can it be.
Just try running 'time' from
Dave Korn wrote:
Just try running 'time' from the bash prompt. You get a SEGV from
strlen
AFAICT.
No, I don't. But I do get a strange behaviour with
time for ((i=0;i=100++)) do :; done
It works fine if you fix the bug :)
I know, which is even more amusing.
Krzysztof Duleba
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Dessent on 1/9/2006 10:29 AM:
$ bash -c time
Segmentation fault (core dumped)
This looks like a bash bug. It looks like only 3.0 is affected, as it works
fine in 3.1. Since 'time' is a builtin, it appears to be a bug in
Eric Blake
Thanks for the backtrace. I'll see about rolling a bash 3.0-15 in the
near future. In the meantime, avoid invalid uses of time (POSIX states
that time takes a mandatory argument of the utility name to run; the
bash
extension of letting time take no arguments was the culprit
Krzysztof Duleba wrote:
near future. In the meantime, avoid invalid uses of time (POSIX states
that time takes a mandatory argument of the utility name to run; the
bash
extension of letting time take no arguments was the culprit here).
This was just a minimal test case.
I think what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Krzysztof Duleba on 1/10/2006 7:14 AM:
This was just a minimal test case.
$ bash -c time ls
Segmentation fault (core dumped)
That is equivalent to 'bash -c time', except that $0 is set to ls
instead of bash or time for the
Eric Blake wrote
This was just a minimal test case.
$ bash -c time ls
Segmentation fault (core dumped)
That is equivalent to 'bash -c time', except that $0 is set to ls
instead of bash or time for the duration of the command
Oh, I wasn't aware of that. Thanks for explanation.
Krzysztof
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
Reproduced on several machines. I wonder what can it be.
Krzysztof Duleba
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On Mon, Jan 09, 2006 at 05:13:54PM +0100, Krzysztof Duleba wrote:
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
Reproduced on several machines. I wonder what can it be.
Just try running 'time'
Christopher Faylor wrote:
Just try running 'time' from the bash prompt. You get a SEGV from strlen
AFAICT.
This doesn't seem to have anything to do with -c. It seems to be an
issue with the time command.
Not my experience:
[EMAIL PROTECTED] ~
$ time
real0m0.000s
user0m0.000s
Krzysztof Duleba wrote:
$ bash -c time
Segmentation fault (core dumped)
$ uname -a
CYGWIN_NT-5.1 DULI2 1.5.19s(0.141/4/2) 20051020 10:37:08 i686 unknown
unknown Cygwin
This looks like a bash bug. It looks like only 3.0 is affected, as it works
fine in 3.1. Since 'time' is a builtin, it
12 matches
Mail list logo