[riot-notifications] [RIOT-OS/RIOT] cpu/msp430_common: Cleanup (#11229)

Marian Buschsieweke notifications at github.com
Thu Mar 21 21:59:02 CET 2019


I ran the test using this modifications:

``` patch
diff --git a/core/sched.c b/core/sched.c
index a5a8d38fb5..bcb0baaad2 100644
--- a/core/sched.c
+++ b/core/sched.c
@@ -37,7 +37,7 @@
 #include "xtimer.h"
 #endif
 
-#define ENABLE_DEBUG (0)
+#define ENABLE_DEBUG (1)
 #include "debug.h"
 
 #if ENABLE_DEBUG
diff --git a/tests/thread_basic/Makefile b/tests/thread_basic/Makefile
index 61bc51c2c4..b393045c97 100644
--- a/tests/thread_basic/Makefile
+++ b/tests/thread_basic/Makefile
@@ -3,6 +3,7 @@ include ../Makefile.tests_common
 BOARD_INSUFFICIENT_MEMORY := nucleo-f031k6
 
 DISABLE_MODULE += auto_init
+USEMODULE += schedstatistics
 
 TEST_ON_CI_WHITELIST += all
 
diff --git a/tests/thread_basic/main.c b/tests/thread_basic/main.c
index 457668095a..c3f7335b89 100644
--- a/tests/thread_basic/main.c
+++ b/tests/thread_basic/main.c
@@ -21,7 +21,7 @@
 #include <stdio.h>
 #include "thread.h"
 
-char t2_stack[THREAD_STACKSIZE_MAIN];
+char t2_stack[THREAD_STACKSIZE_MAIN + THREAD_EXTRA_STACKSIZE_PRINTF];
 
 void *second_thread(void *arg)
 {
```

This is the output. (Apparently the stack of thread 3 is too small of debugging, but I have no idea where that thread is created.)

```
RIOT MSP430 hardware initialization complete.
sched_set_status: adding thread 1 to runqueue 15.
sched_set_status: adding thread 2 to runqueue 7.
sched_run: active thread: 0, next thread: 2
sched_run: done, changed sched_active_thread.
main(): This is RIOT! (Version: 2019.04-devel-587-g9a2f6-msp430_cleanup)
sched_set_status: adding thread 3 to runqueue 6.
first thread

sched_task_exit: ending thread 2...
sched_set_status: removing thread 2 to runqueue 7.
sched_run: active thread: 0, next thread: 3
sched_run: done, changed sched_active_thread.
second thread

sched_task_exit: ending thread 3...
sched_set_status: removing thread 3 to runqueue 6.
sched_run: active thread: 0, next thread: 1
Cannot debug, stack too small
```

What strikes me is the `active thread: 0` in the output.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11229#issuecomment-475399968
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190321/cbea4266/attachment.html>


More information about the notifications mailing list