From 6a6e9d02a312bad94cd164ff7928336472576fec Mon Sep 17 00:00:00 2001 From: Julian Oes Date: Wed, 14 Dec 2016 19:45:45 +0100 Subject: [PATCH] navigator: increase stack The stack size was generally ok but seemed to get exhausted in the case of a waypoint which is too far away and therefore exercises some more code in the mission feasability checker. Generally, we should have more margin in the navigator stack size because there are a bunch of different code paths that can happen. --- src/lib/matrix | 2 +- src/modules/navigator/navigator_main.cpp | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib/matrix b/src/lib/matrix index 34fccdd680..c387e52970 160000 --- a/src/lib/matrix +++ b/src/lib/matrix @@ -1 +1 @@ -Subproject commit 34fccdd6806fbdf7635a6365d7ef112f3bbaab9a +Subproject commit c387e52970b95af8f79795eaeb201e3dcba7284c diff --git a/src/modules/navigator/navigator_main.cpp b/src/modules/navigator/navigator_main.cpp index 361a8510af..28d7c246d8 100644 --- a/src/modules/navigator/navigator_main.cpp +++ b/src/modules/navigator/navigator_main.cpp @@ -673,7 +673,7 @@ Navigator::start() _navigator_task = px4_task_spawn_cmd("navigator", SCHED_DEFAULT, SCHED_PRIORITY_DEFAULT + 5, - 1300, + 1600, (px4_main_t)&Navigator::task_main_trampoline, nullptr);