app-module events & callstack config, crash diagnostics (#630)
- Apps can specify task stack depth and preferred memory placement in their manifests. - App identifiers are validated against length and character requirements. - Crash diagnostics now show the crash cause, reason, fault address, call stack, and program-counter details, with logs saved for review. - App closing is more consistent across built-in screens. There's now a dedicated function, and the old _emit() function is made private. - Crash diagnostics no longer display a QR code without a call stack. - Improved memory allocation for unrestricted requests.
This commit is contained in:
committed by
GitHub
parent
c656ee9ffd
commit
92ca046681
@@ -174,12 +174,7 @@ void onPress(lv_event_t* event) {
|
||||
return;
|
||||
}
|
||||
|
||||
// Async, non-blocking - must NOT call app_manager_stop() directly here: this callback runs
|
||||
// ON the LVGL task, and app-lifecycle transitions must happen on this app's own thread
|
||||
// (woken up via app_event_poll() below), which closes by returning. The result (Ok/Error)
|
||||
// is reported by appMain() itself when it returns, based on ctx.calibrationApplied.
|
||||
AppEvent closeEvent { .type = APP_EVENT_CLOSE, .timestamp = 0, .result = {} };
|
||||
app_event_emit(ctx->appInstanceId, &closeEvent);
|
||||
app_event_emit_close(ctx->appInstanceId);
|
||||
}
|
||||
|
||||
void createWidgets(lv_obj_t* parent, void* userData) {
|
||||
|
||||
Reference in New Issue
Block a user