https://bugzilla.novell.com/show_bug.cgi?id=344584
User ma@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=344584#c9
--- Comment #9 from Michael Andres 2008-03-13 05:32:53 MST ---
Yes. I had a look at the code and spotted that pipe/openpts do not propagate
any error. I fixed it (in SVN:trunk) and introduced:
/** Some detail telling why the execution failed, if it failed.
* Empty if the command is still running or successfully completed.
*
* \li <tt>Can't open pty (%s).</tt>
* \li <tt>Can't open pipe (%s).</tt>
* \li <tt>Can't fork (%s).</tt>
* \li <tt>Command exited with status %d.</tt>
* \li <tt>Command was killed by signal %d (%s).</tt>
*/
const std::string & ExternalProgram::execError() const;
And as well:
/** The command we're executing. */
const std::string & command() const;
Propagating execError in an exception, we should get some reasonable message.
Note: Errors after fork (chroot/exec) are logged to the childs stderr. If this
error output is forwarded to the user, he'll see some reasonable message too.
Otherwise the child exits(129).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.