id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
343	exec deliberately escapes double quotes	dmik		I found out that the `exec*` call (and `spawn` as well I assume) deliberately escapes double quote characters in arguments with a backslash. This is fine for binaries that are built with kLIBC itself as this will be unescaped back before calling `main` (so that the application will not even notice this). However, it screws binaries based on other runtimes (e.g. `rexx.exe` or `wrc.exe`).	defect	new	normal	new	libc	0.6.6	normal