From 310c954779252f01566c9d04ebb9954862b86e9a Mon Sep 17 00:00:00 2001 From: hjk Date: Wed, 6 May 2020 10:27:09 +0200 Subject: [PATCH] Debugger: Make sure to not select frame -1 with LLDB This can appear as (non-existing) preferred frame index in backtraces consisting only of frames without debug info. Fall back to top most frame in that case. Change-Id: Id7bb941d5fc3080aff3853cebb7b92afdd0ba4ea Reviewed-by: Christian Stenger --- share/qtcreator/debugger/lldbbridge.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/share/qtcreator/debugger/lldbbridge.py b/share/qtcreator/debugger/lldbbridge.py index 4434e96c8cb..853ac8c70ee 100644 --- a/share/qtcreator/debugger/lldbbridge.py +++ b/share/qtcreator/debugger/lldbbridge.py @@ -1707,7 +1707,8 @@ class Dumper(DumperBase): def activateFrame(self, args): self.reportToken(args) - self.currentThread().SetSelectedFrame(args['index']) + frame = max(0, int(args['index'])) # Can be -1 in all-asm stacks + self.currentThread().SetSelectedFrame(frame) self.reportResult('', args) def selectThread(self, args):