Remove call to __stdio_exit() in libc (dabt crash randomly)

Author: Daniel Rossier

so3/arch/arm64/traps.c

@@ -118,6 +118,8 @@ typedef void (*vector_fn_t)(cpu_regs_t *);
 
 void trap_handle(cpu_regs_t *regs)
 {
+	int ret = 0;
+
 #ifndef CONFIG_AVZ
 	syscall_args_t sys_args;
 #endif
@@ -141,7 +143,9 @@ void trap_handle(cpu_regs_t *regs)
 	switch (ESR_ELx_EC(esr)) {
 	case ESR_ELx_EC_DABT_LOW:
 
-		dabt_handle(regs, esr);
+		ret = dabt_handle(regs, esr);
+		if (ret == -1)
+			goto __err;
 		break;
 
 	/* SVC used for syscalls */
@@ -247,6 +251,7 @@ void trap_handle(cpu_regs_t *regs)
 #endif
 
 	default:
+__err:
 		lprintk("### On CPU %d: ESR_Elx_EC(esr): 0x%lx\n", smp_processor_id(), ESR_ELx_EC(esr));
 		trap_handle_error(regs->lr);
 		kernel_panic();

so3/kernel/schedule.c

@@ -444,7 +444,8 @@ void schedule(void)
 		LOG_DEBUG("Now scheduling thread ID: %d name: %s PID: %d prio: %d\n", next->tid, next->name,
 			  ((next->pcb != NULL) ? next->pcb->pid : -1), next->prio);
 		if (prev)
-			LOG_DEBUG("Previous was threadID: %d name: %s PID: %d\n", prev->tid, prev->name);
+			LOG_DEBUG("Previous was threadID: %d name: %s PID: %d\n", prev->tid, prev->name,
+				  (next->pcb != NULL) ? next->pcb->pid : -1);
 
 		/*
 		 * The current threads (here prev) can be in different states, not only running; it may be in *waiting* or *zombie*

usr/lib/libc/exit/exit.c

@@ -29,6 +29,15 @@ _Noreturn void exit(int code)
 {
 	__funcs_on_exit();
 	__libc_exit_fini();
+
+#warning __stdio_exit() issue
+	/* 
+	 * Currently, this function causes a data abort fault randomly. The effect
+	 * is visible on RPi4 (64-bit) more rarely on virt64
+	 */
+#if 0
 	__stdio_exit();
+#endif /* 0 */
+
 	_Exit(code);
 }