Minor address environment clean-up. Cannot generate debug contexts in certain contexts

This commit is contained in:
Gregory Nutt 2014-08-27 14:22:00 -06:00
parent a2463148fc
commit d35723749b
3 changed files with 3 additions and 6 deletions

View File

@ -524,7 +524,6 @@ int up_addrenv_select(FAR const group_addrenv_t *addrenv,
uintptr_t paddr;
int i;
bvdbg("addrenv=%p oldenv=%p\n", addrenv, oldenv);
DEBUGASSERT(addrenv);
for (vaddr = CONFIG_ARCH_TEXT_VBASE, i = 0;
@ -682,7 +681,6 @@ int up_addrenv_coherent(FAR const group_addrenv_t *addrenv)
uintptr_t vaddr;
int i;
bvdbg("addrenv=%p\n", addrenv);
DEBUGASSERT(addrenv);
/* Invalidate I-Cache */

View File

@ -152,7 +152,7 @@ static inline int group_addmember(FAR struct task_group_s *group, pid_t pid)
* A thread joins the group when it is created. This is a two step process,
* first, the group must bound to the new threads TCB. group_bind() does
* this (at the return from group_join, things are a little unstable: The
* group has been bound, but tg_nmembers hs not yet been incremented).
* group has been bound, but tg_nmembers has not yet been incremented).
* Then, after the new thread is initialized and has a PID assigned to it,
* group_join() is called, incrementing the tg_nmembers count on the group.
*
@ -189,7 +189,7 @@ int group_bind(FAR struct pthread_tcb_s *tcb)
* A thread joins the group when it is created. This is a two step process,
* first, the group must bound to the new threads TCB. group_bind() does
* this (at the return from group_join, things are a little unstable: The
* group has been bound, but tg_nmembers hs not yet been incremented).
* group has been bound, but tg_nmembers has not yet been incremented).
* Then, after the new thread is initialized and has a PID assigned to it,
* group_join() is called, incrementing the tg_nmembers count on the group.
*

View File

@ -93,8 +93,7 @@
void pthread_release(FAR struct task_group_s *group)
{
FAR struct join_s *join;
sdbg("group=0x%p\n", group);
DEBUGASSERT(group);
/* Visit and delete each join structure still in the list. Since we
* are last exiting thread of the group, no special protection should