os/kernel/task, os/arch/arm/src/common: Fix stack overflow issue when…

… printing TCB list in assert logs

when printing the assert information, the size of stack used for each
TCB is printed wrong and showing stack overflow. This is because when
we are checking the TCB stack, we check from stack_alloc_ptr instead of
stack_base_ptr. So, stack_alloc_ptr points to TLS Data, Arguments and
then available stack whereas stack_base_ptr directly points to available
stack.

Signed-off-by: Neelkumar Patel <neel.patel@samsung.com>

os/arch/arm/src/common/up_checkstack.c

@@ -174,7 +174,7 @@ static size_t do_stackcheck(uintptr_t start, uintptr_t end)
 
 size_t up_check_tcbstack(FAR struct tcb_s *tcb)
 {
-	return do_stackcheck((uintptr_t)tcb->stack_alloc_ptr, (uintptr_t)tcb->adj_stack_ptr);
+	return do_stackcheck((uintptr_t)tcb->stack_base_ptr, (uintptr_t)tcb->adj_stack_ptr);
 }
 
 ssize_t up_check_tcbstack_remain(FAR struct tcb_s *tcb)

os/kernel/task/task_dumptasks.c

@@ -128,7 +128,7 @@ static void task_taskdump(FAR struct tcb_s *tcb, FAR void *arg)
 	lldbg_noarg(TASKDUMP_FORMAT, TASKDUMP_VALUE);
 
 #ifdef CONFIG_STACK_COLORATION
-	if (used_stack_size == tcb->adj_stack_size) {
+	if (used_stack_size >= tcb->adj_stack_size) {
 		lldbg_noarg("  !!! PID (%d) STACK OVERFLOW !!! \n", tcb->pid);
 	}
 #endif