'which' aborts or kills terminal

[engima]

When running the shell command 'which' it will always result in either:

If the command we're trying to find doesn't exit, an error message that some gibberish has been terminated, and also kills the terminal (Attaching screenshot) If the command exists, we just get the terminal closed immediately.

The command 'which' uses, causing the fault is 'echo $(builtin type $cmd | sed lq)'. Typing this out on the command line results in the same problem.

[engima]

Screenshot of error message from 'which asdf'

[jackburton]

I don't know why this was assigned to me, anyway, could be either a problem with the tty layer or with pipes, and in both cases, Axel would know better :)

[wkornewald]

Who is responsible for the Terminal? Currently, the component owner is "jackburton". That's why it got assigned to you.

[axeld]

I've took it over now.

[jackburton]

Typing just echo $($cmd) results in the same problem.

[jackburton]

MiniTerminal is also affected, although:

'which' results in: whence: argument expected

while

'which ls' results in: sh: src/system/libroot/posix/malloc/processheap.cpp:166:void BPrivate::processHeap::free(void *): sb

and a crash.

[bonefish]

Just for reference, this bug might be a symptom of the bug(s) underlying #113 and/or #627.

[bonefish]

Fixed in hrev20402.