Unfortunately, if I try to strace it (strace time ls), I get command not found. If I try to strace `time ls`, I get a hung screen.
Attaching gdb to the running bash session from which I am trying to run time, I don't get any useful pointers, but, what I get is below: (no debugging symbols found) Attaching to program: /bin/bash, process 5647 linux-nat.c:988: internal-error: linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) && WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. I also, for grins, tried sleep 5 && time ls in the bash session and, while it was sleeping, attached the gdb to the bash session, to see if I could get anything that way, and got the below: warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7b122651f000 (no debugging symbols found) 0x000035c7a95e7884 in ?? () Not sure if this helps get any closer, but, thanks! On Thu, Jul 23, 2009 at 8:29 AM, Chet Ramey <chet.ra...@case.edu> wrote: > rjustinwilli...@gmail.com wrote: > > time echo "bah" > > time ls > > time who > > > > Running the commands without the time, they return results as close to > > instantly as I can think of, but, try to time them, in bash, and they > > all hang. > > Since nobody seems to be able to reproduce this, maybe attaching to the > hanging bash process with gdb and doing a stack traceback will provide > better information. > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > > Chet Ramey, ITS, CWRU c...@case.edu > http://cnswww.cns.cwru.edu/~chet/ <http://cnswww.cns.cwru.edu/%7Echet/> >
