On Tue, Aug 2, 2016 at 12:51 PM, <[email protected]> wrote: > Hi Team, > I'm trying to build an OSv application. I have successfully build the same > using capstan. But when I ran the application it prints the following logs > and exits. > > ~/bin/capstan run > Created instance: test > OSv v0.24 > eth0: 192.168.122.15 > vfork() stubbed >
"stubbed" means that OSv has an implementation which is technically correct, but not doing any useful work. In this case, your application called vfork() but all our implementation does is to return an error (-1). OSv does not support fork() or vfork(), as part of its single-process design. It does support threads (pthread_create() etc.). You should check in your application why it wants to fork a new process, and whether you can change it or compile it differently so it doesn't try to fork. In some applications, these "stubbed" messages might not indicate an error at all. The application might receive the error from vfork() (for example) and handle it gracefully - e.g., decide not to fork if it can't. In other applications, forking (for example) might be one of the important things they do, so they cannot continue with the forking having failed. > pthread_setcancelstate() stubbed > > I didn't understand the meaning of the messages. Please help me if I > missed something. > Also do we have logs for the OSv apps to understand the errors if any, > while running? If you run the kernel with the "--verbose" option (I don't know how this is done with "capstan run", someone else on the list might know), you might get additional debugging messages. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
