Bug report for run.exe with patch

["Jonathan Kamens" <jik at kamens dot us>]

Several people have reported problems with run.exe complaining about being
unable to execute programs.

The typical symptoms of the problem are that the user clicks on a link in
the Start menu that uses run.exe and gets back an error pop-up from run.exe
that looks like this:

Error could not start C:\cygwin\bin\emacs-X11.exe [some extra characters
here that shouldn?t be] -display 127.0.0.1:0.0

I just encountered this issue and tracked down the root cause, which is that
run.exe doesn?t null-terminate the data returned by readlink(). According to
the readlink(3) man page on Linux, ?Conforming applications should not
assume that the returned contents of the symbolic link are null-terminated,?
and indeed, at least in some circumstances they are not.

I have attached a patch.

Share and enjoy. :-)

Thanks,

? Jonathan Kamens

Attachment: run-1.1.12-11.readlink.patch
Description: Binary data

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple