labath added a comment.
In D79563#2024854 <https://reviews.llvm.org/D79563#2024854>, @teemperor wrote:
> Changing might actually be a better idea as this way we at least know this
> isn't crashing.
Ok, I'll change the expectation then.
================
Comment at: lldb/packages/Python/lldbsuite/test/lldbinline.py:155
process, lldb.eStopReasonBreakpoint)
- breakpoint_id = thread.GetStopReasonDataAtIndex(0)
- parser.handle_breakpoint(self, breakpoint_id)
+ for id in self._get_breakpoint_ids(thread):
+ parser.handle_breakpoint(self, id)
----------------
vsk wrote:
> nit: I think this leaves the 'id' builtin defined as the last breakpoint id
> after the loop is done, maybe name it something else ('breakpoint_id'?).
yes, of course.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D79563/new/
https://reviews.llvm.org/D79563
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
