labath accepted this revision. labath added a comment. This revision is now accepted and ready to land.
Right. It does bug me a little that this has no test, but I don't think it's the worst that could happen. And you're the one who's going to have to debug this all over again if the next value object change breaks swift again. In D83450#2142114 <https://reviews.llvm.org/D83450#2142114>, @jingham wrote: > I'm planning on continuing to dig into this stuff, and hopefully come up with > something more coherent. But your fix is needed for ValueObjectVariables to > avoid crashes when debugging optimized code, and so I need a short-term way > to get it to work but not cause problems for Synthetic values. This fix is > mostly correct. TTTT, I think if you were being more rigorous about this > direction of fix, you would have UpdateChildrenAddressType walk back up the > parent hierarchy asking at each level whether the parent knows where its > pointer children should be found. But that's adding complexity that doesn't > solve any actual problem, and we'd probably end up ripping it out again in a > better solution. Yes, I've been wondering if something like that wasn't needed, but I wasn't sure how all the parent-child relationships work... Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D83450/new/ https://reviews.llvm.org/D83450 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
