sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Disable the vfork() OS test... it fails

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5489 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2013-01-07 23:09:09 +00:00
parent 190e47d637
commit 7408f8da44
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
arch/arm/src/common/up_vfork.c
View File

@ -169,7 +169,11 @@ pid_t up_vfork(struct vfork_s *context)
return (pid_t)ERROR; return (pid_t)ERROR;
} }
/* How much of the parent's stack was utilized? */ /* How much of the parent's stack was utilized? The ARM uses
* a push-down stack so that the current stack pointer should
* be lower than the initial, adjusted stack pointer. The
* stack usage should be the difference between those two.
*/
DEBUGASSERT((uint32_t)parent->adj_stack_ptr > context->sp); DEBUGASSERT((uint32_t)parent->adj_stack_ptr > context->sp);
stackutil = (uint32_t)parent->adj_stack_ptr - context->sp; stackutil = (uint32_t)parent->adj_stack_ptr - context->sp;
@ -177,7 +181,7 @@ pid_t up_vfork(struct vfork_s *context)
svdbg("stacksize:%d stackutil:%d\n", stacksize, stackutil); svdbg("stacksize:%d stackutil:%d\n", stacksize, stackutil);
/* Make some feeble effort to perserve the stack contents. This is /* Make some feeble effort to perserve the stack contents. This is
* feeble because the stack surely contains invalid pointer and other * feeble because the stack surely contains invalid pointers and other
* content that will not work in the child context. However, if the * content that will not work in the child context. However, if the
* user follows all of the caveats of vfor() usage, even this feeble * user follows all of the caveats of vfor() usage, even this feeble
* effort is overkill. * effort is overkill.