This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I would like to point out a regression, seemingly introduced in 1.7.10. If a program is exec'ed after forking in a thread and the program is a native Windows program, it (seemingly) fails to start. Please, find attached a test case. You can try it with gvim, for example. There's no problem with the cygwin version of gvim: $ ./fork_in_thread /usr/bin/gvim but trying to start the native windows version: $ ./fork_in_thread "/cygdrive/c/Program Files/Vim/vim73/gvim" fails, in the sense that nothing happens and no error is reported. A workaround here is using env. Indeed, the following works: $ ./fork_in_thread env "/cygdrive/c/Program Files/Vim/vim73/gvim" However, what puzzles me is the fact that a wrapper (like the one below) starting gvim by using system() and compiled with i686-pc-mingw32-gcc works, too! All the previous examples were working in 1.7.9. ----- wrapper.c ----- #include <stdio.h> int main(void) { system("\"C:/Program Files/Vim/vim73/gvim\""); return 0; } --------------------- -- Enrico
Attachment:
fork_in_thread.c
Description: Text document
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |