Christopher Faylor wrote:
> That's not guaranteed fork behavior. If the child never started, that would
> be a bug.
As you can see in my previous post, the programm is really simple :
a loop of printf for the child, a loop of printf for the father.
There's no place for a bug here ...
> There
An interresting part of strace traces of the programm show well that the
child didn't start before the death of his father :
260> Je suis le pere 9991
260> Je suis le pere 9992
260> Je suis le pere 9993
260> Je suis le pere 9994
260> Je suis le pere 9995
260> Je suis le pere 9996
260> Je suis le
Hello,
Because my problems with fork and DLL continue, I tried to remove
DLL and to test only fork.
And Cygwin had a really different behavior than unix has.
With the programm below I have 1000 times "Je suis le fils" and then
1 times "Je suis le pere" or the reverse sometimes.
Under my
cgf wrote :
> signals do not work with anything but the main thread. Sorry.
>
Is this a temporary behavior or will it work in the futur ?
What are the other limits of non-main threads ?
Has new processes created by fork the same limits ? others ?
Stephane
--
Unsubscribe info: http:/
Hello,
If I fork my programm,
the child died when it call a function in a DLL. (Cygwin 1.3.10-1 on
NT4)
void dll_call(int i)
{
printf("in dll_call %d\n", i);
}
...
printf("begin");
switch (pid=fork())
{
case 0 :
printf("child is alive\n");
Kohn Emil Dan wrote:
> Hello everyone,
>
> I would like to report a problem with g++ static member initialization on
> cygwin. I have a class in which I have a static data member. The
> definition of that class resides in a DLL. That static member is
> initialized in the corresponding .cpp file.
I don't know if my compagny will be OK to maintain it in the futur,
but now we need it. It's why we will try to debug sunRPC for the current
version.
Does anybody know why it doesn't work ?
Any help or even an idea is welcome.
Stephane
Corinna Vinschen wrote:
> On Fri, Mar 01, 2002 at 04:58:3
7 matches
Mail list logo
