Re: vfork always fail problem

2010-05-26 Thread Corinna Vinschen
On May 19 00:07, Kazuhiro Fujieda wrote: > >>> On Tue, 18 May 2010 10:31:36 -0400 > >>> Christopher Faylor said: > > >>2010-05-18 Kazuhiro Fujida > > I mistyped my name in ChangeLog. > Please correct Fujida to Fujieda on the first opportunity. Done. Corinna -- Corinna Vinschen

Re: vfork always fail problem

2010-05-26 Thread Corinna Vinschen
On May 20 11:43, Huang Bambo wrote: > 2010/5/20 Huang Bambo : > >> Huang, > >> > >> you - as the person who first saw and documented the problem in public > >> (thank you!) - are in the best position to test it, if you can recreate the > >> original situation (with the GBK(?) directory names). > >>

Re: vfork always fail problem

2010-05-19 Thread Huang Bambo
2010/5/20 Huang Bambo : >> Huang, >> >> you - as the person who first saw and documented the problem in public >> (thank you!) - are in the best position to test it, if you can recreate the >> original situation (with the GBK(?) directory names). >> >> It would be beneficial to all of us, and you w

Re: vfork always fail problem

2010-05-19 Thread Huang Bambo
> Huang, > > you - as the person who first saw and documented the problem in public > (thank you!) - are in the best position to test it, if you can recreate the > original situation (with the GBK(?) directory names). > > It would be beneficial to all of us, and you would be doing everybody a > fav

Re: vfork always fail problem

2010-05-19 Thread Matthias Andree
Huang Bambo wrote on 2010-05-19: http://cygwin.com/snapshots/ To the OP: please check it out and verify that it solves your problem. Thanks a lot. I've changed my work directory to a full English name directory and it dosn't matter me. And this problem is first reported by gcc, strange :

Re: vfork always fail problem

2010-05-18 Thread Huang Bambo
>  http://cygwin.com/snapshots/ > > To the OP: please check it out and verify that it solves your problem. > Thanks a lot. I've changed my work directory to a full English name directory and it dosn't matter me. And this problem is first reported by gcc, strange :) . > cgf > > -- > Problem report

Re: vfork always fail problem

2010-05-18 Thread Christopher Faylor
On Tue, May 18, 2010 at 08:45:26AM -0600, Eric Blake wrote: >On 05/18/2010 08:31 AM, Christopher Faylor wrote: >>> >>> - WCHAR corefile[strlen (p) + sizeof (".stackdump")]; >>> + WCHAR corefile[wcslen (p) + sizeof (L".stackdump")]; >> ^^

Re: vfork always fail problem

2010-05-18 Thread Kazuhiro Fujieda
>>> On Tue, 18 May 2010 10:31:36 -0400 >>> Christopher Faylor said: >>2010-05-18 Kazuhiro Fujida I mistyped my name in ChangeLog. Please correct Fujida to Fujieda on the first opportunity. >>- WCHAR corefile[strlen (p) + sizeof (".stackdump")]; >>+ WCHAR corefile[wcslen (p) + sizeof

Re: vfork always fail problem

2010-05-18 Thread Eric Blake
On 05/18/2010 08:31 AM, Christopher Faylor wrote: >> >> - WCHAR corefile[strlen (p) + sizeof (".stackdump")]; >> + WCHAR corefile[wcslen (p) + sizeof (L".stackdump")]; > ^^ > No L" is needed here, AFAICT. > > I've checked this in, re

Re: vfork always fail problem

2010-05-18 Thread Christopher Faylor
On Tue, May 18, 2010 at 02:47:57PM +0900, Kazuhiro Fujieda wrote: On Fri, 14 May 2010 21:22:02 +0200 Corinna Vinschen said: > >> That sounds a bit weird. The joke of using the ...W functions is that >> the string parameters are always given in UTF-16. GBK is a multibyte >> charset and c

Re: vfork always fail problem

2010-05-18 Thread Kazuhiro Fujieda
>>> On Fri, 14 May 2010 21:22:02 +0200 >>> Corinna Vinschen said: > That sounds a bit weird. The joke of using the ...W functions is that > the string parameters are always given in UTF-16. GBK is a multibyte > charset and can only be used in conjunction with the ...A functions. > However, I'm o

Re: vfork always fail problem

2010-05-14 Thread Corinna Vinschen
On May 14 16:54, Huang Bambo wrote: > I's the problem of the fork() pass a wrong program path to CreateProcessW. > > It shoud pass a GBK code pathname to CreateProcessW but if I set > LANG=en_US.UTF-8, the pathname passed to CreateProcessW is UTF-8, so > CreateProcessW report file not found. Tha

Re: vfork always fail problem

2010-05-14 Thread Huang Bambo
I's the problem of the fork() pass a wrong program path to CreateProcessW. It shoud pass a GBK code pathname to CreateProcessW but if I set LANG=en_US.UTF-8, the pathname passed to CreateProcessW is UTF-8, so CreateProcessW report file not found. 2010/5/14 Matthias Andree : > Am 14.05.2010, 06:

Re: vfork always fail problem

2010-05-14 Thread Matthias Andree
Am 14.05.2010, 06:29 Uhr, schrieb Huang Bambo: [ba...@bambo-notebook 4.4.4]$ cat tvfork.c #include #include #include int main(void) { pid_t pid = vfork(); if ( pid > 0 ) { printf("I'm chield.\n"); _exit(0); } else if ( p

Re: vfork always fail problem

2010-05-13 Thread Václav Haisman
Huang Bambo wrote, On 14.5.2010 6:29: > [ba...@bambo-notebook 4.4.4]$ cat tvfork.c > #include > #include > #include > > int main(void) > { > pid_t pid = vfork(); > if ( pid > 0 ) > { > printf("I'm chield.\n"); > _exit(0); > } >

Re: vfork always fail problem

2010-05-13 Thread Huang Bambo
I truly find the problem. The path to the executable have Chinese character. My windows's default language is gbk. If I use utf-8 encoding for the shell, fork fail. If i use gbk, everything goes fine. The following is the test . [ba...@bambo-notebook ARM9]$ pwd /cygdrive/d/个人研发/ARM9

Re: vfork always fail problem

2010-05-13 Thread Huang Bambo
Finally I test and get another result. I run the test program at /home/Bambo/test/t1/ but /home/Bambo/test is a symbolic link to another directory. Maybe it's the problem that the system handle symbolic 2010/5/14 Huang Bambo : > [ba...@bambo-notebook 4.4.4]$ cat tvfork.c > #include > #include >