On Tue, 4 Feb 2003, Terry Lambert wrote:
> rmkml wrote:
> > Thank for you answer.
>
> Sorry that it probably was not the answer you wanted. 8-(.
>
>
> > It is difficult to find anything concerning the signal model
> > of BSD implementation. In particular, for threaded applications.
> > If you
rmkml wrote:
> Thank for you answer.
Sorry that it probably was not the answer you wanted. 8-(.
> It is difficult to find anything concerning the signal model
> of BSD implementation. In particular, for threaded applications.
> If you can give me some advise or documentation to read, it will
>
Thank for you answer.
It is difficult to find anything concerning the signal model
of BSD implementation. In particular, for threaded applications.
If you can give me some advise or documentation to read, it will
be very helpfull to me .
In the first part of the answer, do you want to say that a
rmkml wrote:
> here is a sample code (vfork_execve.c) to demonstrate a locking problem.
The short answer is that your code is wrong.
The longer answer is that your code is assuming implementation
details in vfork() which are undefined in threaded programs,
according to the standard, and is assumi
ok sorry, change on Makefile :
CCFLAGS=$(CCFLAGS_BSD)
LIBS= $(LIB_THREAD_BSD) $(LIB_BSD)
Regards.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
here is a sample code (vfork_execve.c) to demonstrate a locking problem.
The code launch 3 threads :
1 signal
2 endless do nothing
3 a socket server (bind to 127.0.0.1:12345)
The server accept 3 cmd:
1) close => close cnx
2) sleep => use vfork /execv to launch external "/bin/sleep 20"
to r
6 matches
Mail list logo
