en Copyright 2015 Java http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/functionalities/bt-interrupt/Makefile#e19387e6936c9ccc6200b32f3affea7b1020664c We can't let GetStackFrameCount get interrupted or it will give thewrong answer. Plus, it's useful in some places to have a way to forcethe full stack to be created even in the face ofinterruption. Moreover, most of the time when you're just gettingframes, you don't need to know the number of frames in the stack tostart with. You just keep callingThread::GetStackFrameAtIndex(index++) and when you get a nullStackFrameSP back, you're done. That's also more amenable tointerruption if you are doing some work frame by frame.So this patch makes GetStackFrameCount always return the full count,suspending interruption. I also went through all the places that useGetStackFrameCount to make sure that they really needed the full stackwalk. In many cases, they did not. For instance frame select -r 10 wasgetting the number of frames just to check whether cur_frame_idx + 10was within the stack. It's better in that case to see if that frameexists first, since that doesn't force a full stack walk, and onlydeal with walking off the end of the stack if it doesn't...I also added a test for some of these behaviors.Differential Revision: https://reviews.llvm.org/D150236 List of files: /llvm-project/lldb/test/API/functionalities/bt-interrupt/Makefile Thu, 11 May 2023 00:48:48 +0000 Jim Ingham <jingham@apple.com>